Security

Rolle IT Successfully Completes CMMC Level 2 C3PAO Assessment

A CMMC Level 2 Assessed MSSP and MSP Supporting the Defense Industrial Base

Rolle IT is proud to announce that we have successfully completed our CMMC Level 2 assessment conducted by a C3PAO, achieving Final CMMC Level 2 status for our assessed environment.

For Rolle IT, this is more than a compliance milestone.

It represents firsthand experience that we can bring directly to the defense contractors, manufacturers, engineering firms, and other organizations we support throughout the Defense Industrial Base.

Rolle IT is a CMMC Level 2 assessed Managed Security Service Provider (MSSP) and Managed Service Provider (MSP) focused on helping Defense Industrial Base organizations protect Controlled Unclassified Information (CUI), build secure environments, and prepare for CMMC.

We’ve helped clients through their CMMC journeys.

Now we’ve been through the assessment ourselves.

Among the Early Organizations to Complete CMMC Level 2

The scale of CMMC implementation across the Defense Industrial Base is significant.

The Cyber AB estimates that the broader Defense Industrial Base includes approximately 200,000 to 300,000 companies, although not every DIB organization will face the same CMMC requirement. [https://cy…-Ecosystem]

Based on Department of Defense CMMC Program Final Rule projections, approximately 78,000 organizations are expected to fall within the population requiring CMMC Level 2 third-party assessment or the higher Level 3 pathway that first requires Final Level 2 status. [federalregister.gov], [public-ins…gister.gov]

Using an October 2026 industry benchmark of approximately 2,700 completed and pending Level 2 assessments, that represents roughly 3.5% of the projected 78,000-organization population.

Rolle IT is among this early group and has successfully completed its third-party CMMC Level 2 C3PAO assessment.

Put simply, while tens of thousands of organizations are expected to move through CMMC Level 2 requirements, Rolle IT has already done it.

An Even Smaller Group Among MSPs and MSSPs

That distinction becomes even more meaningful when looking specifically at managed service providers.

Based on identified industry tracking, fewer than 100 MSPs nationwide have achieved this milestone through a CMMC Level 2 C3PAO assessment.

Rolle IT is now among them.

That matters because an MSP or MSSP supporting a defense contractor can have extensive responsibility for the systems that underpin the customer’s security program. Your provider may help administer identities, endpoints, networks, cloud environments, security tools, monitoring, incident response, and the systems used to protect CUI.

Defense contractors should therefore ask an important question when evaluating a CMMC technology or cybersecurity partner:

Has the company helping us prepare for CMMC gone through the CMMC assessment process itself?

For Rolle IT, the answer is yes.

We Don’t Just Understand CMMC. We’ve Been Through It.

There is a significant difference between understanding CMMC requirements and putting your own environment in front of an independent C3PAO.

Our team had to demonstrate our own environment.

Our documentation, our security controls, our System Security Plan. our policies and procedures, our evidence and the operational practices supporting them.

That experience reinforced many of the principles we’ve emphasized when helping our own clients prepare for CMMC.

The technology, documentation, evidence, people, and everyday business practices all have to work together.

CMMC Is Not Simply an IT Project

Cybersecurity technology is an important component of CMMC, but technology alone cannot create a compliant organization.

Rolle IT is here to help your organization through CMMC. [email protected] for more information.

Rolle IT Successfully Completes CMMC Level 2 C3PAO Assessment Read More »

CMMC Enclaves for the Defense Industrial Base: Why Your MSSP Matters

Rolle IT Designs, Builds, Secures, and Manages CMMC Enclaves for Defense Contractors

For organizations in the Defense Industrial Base preparing for Cybersecurity Maturity Model Certification, determining how and where Controlled Unclassified Information (CUI) will be handled is one of the most important decisions in the CMMC journey.

For many small and midsized defense contractors, a CMMC enclave can provide a practical approach.

Rolle IT designs, builds, secures, documents, and manages CMMC enclaves for Defense Industrial Base organizations that need to protect CUI and meet CMMC requirements.

Rolle IT is also a CMMC Level 2 assessed Managed Security Service Provider (MSSP) and Managed Service Provider (MSP) serving the Defense Industrial Base.

That means our perspective is not limited to designing CMMC environments for customers. We have supported clients through their CMMC journeys, and we have applied the same security, documentation, evidence, and operational disciplines within our own environment.

For defense contractors looking for a CMMC enclave solution, that experience matters.

What Is a CMMC Enclave?

A CMMC enclave is a defined environment designed to limit where CUI is accessed, processed, transmitted, and stored.

Rather than allowing CUI to move throughout an organization’s broader IT environment, an enclave can establish a controlled boundary around the people, systems, applications, and data that require access to CUI.

For example, a defense contractor may have 100 employees, but perhaps only 15 need to access CUI. Instead of unnecessarily introducing CUI into systems used across the entire company, the organization may be able to design a secure enclave around those specific users and workflows.

The objective is not simply isolation.

A properly designed CMMC enclave should give the organization a secure, usable, supportable, and clearly understood environment for handling CUI.

Rolle IT Builds CMMC Enclaves Around the Business

There is no single CMMC enclave design that makes sense for every defense contractor.

That is why Rolle IT starts with the CUI workflow rather than a predetermined technology stack.

Before designing an enclave, we want to understand questions such as:

  • What CUI does the organization receive?
  • Where does CUI enter the business?
  • Who needs access to it?
  • Where does the information need to be stored?
  • Which applications are required to perform the work?
  • Does CUI need to be exchanged with customers, DoD organizations, primes, or subcontractors?
  • Do employees need to print or otherwise work with physical CUI?
  • Which endpoints need access?
  • What should be inside and outside the enclave boundary?
  • How will users perform their jobs without unnecessarily expanding the CUI environment?

Those answers help determine the right architecture.

Depending on the organization’s requirements, that architecture may involve technologies such as Microsoft 365 GCC High and security capabilities for identity, endpoints, networking, access control, monitoring, logging, and incident response.

But technology comes after understanding the requirement.

We do not believe a CMMC enclave should be a collection of security products looking for a problem to solve.

A CMMC Enclave Is More Than a GCC High Tenant

One misconception worth addressing directly is that purchasing Microsoft 365 GCC High creates a CMMC enclave.

It does not.

GCC High can be an important component of an organization’s CUI strategy, but the complete environment has to be considered.

A defense contractor still needs to understand its endpoints, identities, network, applications, administrative access, CUI flows, security monitoring, physical processes, policies, procedures, documentation, and operational responsibilities.

That’s why Rolle IT approaches the enclave as an environment, not simply a Microsoft licensing project.

The SSP Should Describe the Enclave You Actually Built

Technical architecture and CMMC documentation should not exist independently.

The organization’s System Security Plan (SSP) should accurately explain how security requirements are implemented within that specific environment.

For Rolle IT, this creates a very important connection:

Requirement → Architecture → Implementation → Documentation → Evidence

If our team helps make a technical or architectural decision, we want to understand how that decision relates to the applicable security requirement.

That means our engineers and security professionals are not simply reading an SSP later and trying to figure out why something was implemented.

We understand the why behind the environment.

That institutional knowledge becomes extremely valuable during both assessment and ongoing operations.

Build Your Enclave With Assessment in Mind

Assessment readiness should not begin when the C3PAO assessment is scheduled.

It should begin while the environment is being designed.

As the enclave is built, Rolle IT places an emphasis on documentation and evidence collection so there is a logical connection between what the SSP says and what exists within the technical environment.

When an assessor needs to understand how a requirement is satisfied, the organization should be positioned to explain:

Here is the requirement.

Here is how we implemented it.

Here is where we documented it.

Here is who is responsible for it.

Here is the evidence that supports it.

The objective is to make the environment understandable and the supporting information easy to locate.

We’ve supported clients using this approach, and we have experienced its value during our own CMMC Level 2 assessment.

Why Your CMMC Enclave Needs an MSSP

Building the enclave is only the first step.

Once the environment goes live, real life begins.

Employees join and leave.

Applications change.

Endpoints need to be replaced.

Firewall rules change.

New contracts introduce new workflows.

Vulnerabilities are identified.

Security events need investigation.

Users need support.

Documentation needs updating.

Evidence needs to continue being maintained.

That’s why we believe a CMMC enclave benefits from an MSSP that understands why the environment was designed the way it was.

Consider a seemingly simple request:

“Can you give this employee access to this application?”

A traditional IT response may focus primarily on making the application work.

Within a CMMC enclave, Rolle IT can consider the request in a broader context:

  • Will CUI enter the application?
  • Where is the application’s data stored?
  • Does the application affect the enclave boundary?
  • Does it introduce another system into scope?
  • Does the CUI flow change?
  • Does the SSP need to be updated?
  • Are new controls or evidence required?
  • Does the change introduce additional security risk?

The technical answer may still be yes.

But a decision involving a CMMC environment should be made with an understanding of its broader implications.

One Partner From Enclave Design Through Ongoing Security

Rolle IT can support the CMMC enclave throughout its lifecycle.

CMMC Enclave Design

We help determine how CUI needs to move through the organization and design an environment around those requirements.

CMMC Enclave Implementation

We build and configure the technologies necessary to establish the environment and its security boundaries.

Microsoft 365 GCC High

Where appropriate, Rolle IT can incorporate Microsoft 365 GCC High into the organization’s CUI environment and support its ongoing administration.

CMMC Documentation and SSP Support

We help connect the technical environment to the SSP and supporting policies and procedures so the documentation reflects how the environment actually operates.

CMMC Evidence Organization

We help establish an organized relationship between requirements, implementations, documentation, and supporting evidence.

Managed IT Services

As an MSP, Rolle IT can support the users, devices, systems, and Microsoft environment that keep the enclave operational.

Managed Security Services

As an MSSP, Rolle IT can provide ongoing cybersecurity capabilities around the environment, including monitoring, security operations, vulnerability management, and incident response support.

Ongoing CMMC Support

When the environment changes, we can help organizations understand how those changes potentially affect security, documentation, evidence, and CMMC requirements.

We’ve Built These Environments for Clients. We’ve Gone Through CMMC Ourselves.

This is an important distinction for organizations choosing a CMMC enclave provider.

Rolle IT’s experience does not come only from studying the CMMC framework.

We have helped clients build, secure, document, and prepare CMMC environments successfully.

And we have applied those principles to ourselves.

Rolle IT is a CMMC Level 2 assessed MSSP and MSP serving the Defense Industrial Base.

We have experienced the C3PAO assessment process firsthand.

We understand the importance of a well-defined environment, accurate SSP, organized evidence, knowledgeable technical team, and security program that operates the way its documentation says it operates.

When we tell clients that assessment readiness should be built into their environment from the beginning, that recommendation comes from experience on both sides.

Looking for a CMMC Enclave Provider?

If your organization is searching for a CMMC enclave provider, CMMC MSSP, CMMC MSP, GCC High provider, CMMC Level 2 technology partner, or managed cybersecurity provider for the Defense Industrial Base, Rolle IT can help.

We work with defense contractors to:

  • Design CMMC enclaves
  • Build secure CUI environments
  • Implement and support Microsoft 365 GCC High
  • Establish secure enclave boundaries
  • Implement cybersecurity controls
  • Develop and maintain supporting documentation
  • Align the SSP with the actual technical environment
  • Organize CMMC evidence
  • Prepare the environment for C3PAO assessment
  • Provide ongoing managed IT support
  • Provide ongoing managed security services

Our objective is not simply to build an environment that looks ready for assessment.

It is to build an environment your business can actually use, your team can explain, your assessor can understand, and your organization can continue to secure and operate after the assessment is over.

Talk to Rolle IT About Your CMMC Enclave

A CMMC enclave represents an important investment in your organization’s ability to protect CUI and continue supporting the Defense Industrial Base.

Choose a partner that understands what happens before, during, and after the build.

Rolle IT designs, builds, documents, secures, and manages CMMC enclaves for the Defense Industrial Base.

And because we have gone through the CMMC Level 2 assessment process ourselves, we understand the environment from the technology underneath it to the evidence that supports it.

Rolle IT Is Among the Early CMMC Level 2 Organizations

The scale of CMMC implementation across the Defense Industrial Base is significant. The Department of Defense’s projections indicate that roughly 78,000 organizations are expected to require CMMC Level 2, with the vast majority requiring a third-party C3PAO certification assessment and a smaller population subject to other Level 2 assessment requirements. [federalregister.gov]

Using the approximately 2,700 completed and pending Level 2 assessments reported by October 2026 as the current industry benchmark, only about 3.5% of that projected Level 2 population has reached or entered the formal assessment process.

That places Rolle IT among the first 4% of the projected CMMC Level 2 population to move through this process, and Rolle IT has successfully completed the more rigorous third-party C3PAO assessment.

For us, that distinction matters.

Rolle IT didn’t simply prepare for CMMC or rely on a self-assessment. We placed our own environment, security controls, System Security Plan, policies, procedures, and evidence in front of an independent C3PAO and successfully completed the CMMC Level 2 assessment process.

That experience is now part of what Rolle IT brings to its customers.

As a CMMC Level 2 assessed MSSP and MSP serving the Defense Industrial Base, Rolle IT helps defense contractors design and build CMMC enclaves, protect CUI, implement security controls, support Microsoft 365 GCC High environments, develop SSP documentation, organize assessment evidence, prepare for C3PAO assessment, and manage those environments after the assessment is complete.

We don’t just help organizations understand CMMC. We have built it, documented it, operated under it, provided the evidence for it, and successfully gone through the third-party assessment ourselves.

Less than 100 Identified MSPs around the country have achieved this milestone. [email protected] for more information.

CMMC Enclaves for the Defense Industrial Base: Why Your MSSP Matters Read More »

CMMC Documentation Should Make the Assessment Easier, Not Harder

How Rolle IT Builds Documentation, Evidence, and Institutional Knowledge Into CMMC Environments

When a CMMC assessment begins, an organization should not have to scramble to determine where its evidence is, which policy addresses a requirement, how a control is implemented, or why a particular security decision was made.

The technology may be in place and the security controls may be functioning exactly as intended. But if the organization cannot clearly explain and demonstrate how those controls satisfy the requirements identified in its System Security Plan (SSP), the assessment process becomes more difficult than it needs to be.

At Rolle IT, we approach CMMC documentation differently.

The SSP, supporting policies and procedures, technical implementation, and evidence collection are developed as interconnected parts of the same security program.

It is an approach we have successfully used in supporting clients through CMMC, and it is the same discipline we applied within our own environment as Rolle IT completed its CMMC Level 2 C3PAO assessment.

Today, Rolle IT is a CMMC Level 2 assessed Managed Security Service Provider (MSSP) and Managed Service Provider (MSP) serving the Defense Industrial Base.

That distinction matters. We are not simply advising organizations on what assessment readiness should look like. We have helped clients through the process, and we have gone through it ourselves.

The SSP Should Tell the Story of the Environment

A System Security Plan should never feel like a collection of generic responses to CMMC requirements.

It should tell the story of the actual security environment.

Where does CUI reside? Who can access it? What systems are within scope? What protects the boundary? How is access granted and removed? How are systems monitored? What happens when something goes wrong? Who owns each responsibility?

Most importantly, why was the environment designed this way?

That last question is frequently overlooked.

When Rolle IT helps build and manage a CMMC environment, our team becomes deeply familiar with both the how and the why behind the decisions captured in the SSP.

We understand why CUI is restricted to particular systems, why a specific access model was selected, how identity is managed, why certain users or devices are excluded from the environment, where security logs are collected, how incidents are escalated, and what evidence demonstrates that these processes are actually occurring.

The SSP is not separate from that knowledge. It is the documented expression of it.

Documentation Should Be Created Alongside the Environment

One of the easiest ways to make a CMMC assessment unnecessarily difficult is to wait until assessment time to organize the documentation.

When documentation is written after the fact, people are forced to reconstruct decisions that may have been made months or years earlier.

Why was this configured this way?

Who approved this process?

Does the policy actually match what the technical team is doing?

Where is the evidence?

At Rolle IT, documentation and evidence collection are incorporated into the process of building and managing the environment.

As technical decisions are made, they are documented. As processes are established, ownership is identified. As controls are implemented, the team considers how their implementation will be demonstrated.

That creates a logical progression:

Requirement → Implementation → Documentation → Evidence

Each element supports the next.

And because our team participates in that process, our knowledge extends beyond what is written on the page. We understand the reasoning behind the implementation.

Evidence Should Be Easy to Find

Evidence collection should not become a scavenger hunt in the weeks leading up to an assessment.

A security requirement might be properly implemented, but an assessor still needs to be able to evaluate that implementation.

The supporting artifact could be a configuration, system export, ticket, log, approval, training record, screenshot, report, policy, procedure, or another source of evidence.

The important question is not simply:

“Are we doing this?”

It is also:

“How do we demonstrate that we are doing this?”

Rolle IT’s approach is to consider evidence as part of the implementation and ongoing management of the control.

Documentation and evidence are organized so the team can move logically from a requirement, to the SSP implementation statement, to the systems or processes involved, and finally to the artifacts that support it.

When an assessor asks how a requirement is satisfied, the answer should not be:

“We know we’re doing that. Give us some time to find something.”

The goal is to be able to say:

“Here is how we satisfy the requirement. Here is where it is documented. Here is how it is implemented. Here is who is responsible. And here is the evidence.”

That level of organization helps make the assessment process clearer for everyone involved.

Make It Easy for the Assessor to Understand Your Environment

A well-organized assessment environment isn’t about creating more documentation.

It is about creating clarity.

Assessors need to understand what the organization has implemented and evaluate whether it satisfies the applicable CMMC requirements. Clear SSP statements, coordinated policies and procedures, organized evidence, and knowledgeable people make that process more efficient.

The objective should never be to overwhelm an assessor with hundreds of files.

The objective is to make the right information easy to locate, understand, and validate.

That is why Rolle IT places so much emphasis on organizing documentation and evidence before assessment day.

The Difference Is Knowing the “What,” the “How,” and the “Why”

This is also where Rolle IT’s role as an ongoing MSSP and MSP creates significant value for organizations within the DIB.

Our team does not simply need to know that a control exists.

We work to understand:

  • What the CMMC requirement is intended to accomplish.
  • How that requirement is implemented within the client’s environment.
  • Why the technical and operational decisions behind that implementation were made.
  • Where those decisions are documented in the SSP, policies, and procedures.
  • Who is responsible for maintaining the process.
  • What evidence can demonstrate that the documented implementation is functioning as intended.

That institutional knowledge matters.

When something changes six months after the assessment, our team isn’t simply looking at an old SSP and trying to determine what its authors intended. We understand the environment and the reasoning behind its design.

That allows us to consider not only the immediate technical impact of a change, but also its potential impact on the organization’s CMMC scope, SSP, supporting documentation, evidence, and security posture.

We’ve Done This With Our Clients, and We’ve Done It Ourselves

Perhaps the most important perspective we can bring to a DIB organization is experience from both sides of the process.

Rolle IT has used this approach to help clients successfully navigate CMMC requirements and assessments.

We have also applied those disciplines to ourselves.

Going through our own CMMC Level 2 C3PAO assessment reinforced the importance of documentation that reflects the real environment and evidence that is organized, accessible, and connected to the requirements it supports.

Our team didn’t have to learn the environment from an SSP shortly before assessment.

We knew the environment because we built, operated, secured, documented, and maintained it.

That is now the experience Rolle IT brings to the Defense Industrial Base as a CMMC Level 2 assessed MSSP and MSP.

Assessment Readiness Should Be Built Into the Environment

Preparing for a CMMC assessment should not begin when the assessment is placed on the calendar.

It should begin when the environment is designed.

It should continue when controls are implemented.

It should be reinforced when policies and procedures are created.

It should be supported every time evidence is collected.

And it should continue as the environment changes after the assessment is complete.

Your team should never have to reconstruct the story of your CMMC program for an assessor. The story should already be documented, understood, implemented, and supported by evidence.

At Rolle IT, we have seen the value of that approach in the environments we support, and we have experienced it firsthand through our own CMMC Level 2 assessment.

For Defense Industrial Base organizations preparing for CMMC, that’s the perspective we bring to the table: we know what it takes to prepare an environment for assessment because we’ve helped our clients do it successfully, and we’ve done it ourselves.

Contact Rolle IT [email protected] for more information.

CMMC Documentation Should Make the Assessment Easier, Not Harder Read More »

Beyond IT: Building a Culture of Security Compliance

One of the most important lessons reinforced through our own CMMC journey is that compliance cannot live solely within the IT department.

Technology is certainly an essential part of protecting CUI. Secure systems, access controls, identity management, endpoint protection, monitoring, and incident response all play critical roles. But technology alone cannot make an organization compliant.

True compliance is reflected in how an organization operates every day.

It is found in the way employees handle sensitive information, how leadership establishes expectations, how access is granted and removed, how new employees are onboarded, how incidents are reported, how vendors are managed, and whether documented policies accurately reflect what people actually do.

In other words, compliance is not simply a collection of security controls. It is an organizational discipline.

That means responsibility for CMMC cannot rest exclusively with IT. Leadership must establish accountability. Operations must incorporate security into business processes. Human resources must understand its role in personnel security and access. Employees must recognize their individual responsibility for protecting information. IT and cybersecurity teams provide the technical foundation that enables all of those pieces to work together.

This is why CMMC cannot simply be handed to an IT provider with the expectation that they will “make the company compliant.”

As an MSSP supporting the Defense Industrial Base, Rolle IT’s responsibility is to help organizations build and maintain the secure technical foundation their compliance program depends upon. We can help identify gaps, implement and manage security controls, protect CUI environments, monitor for threats, support evidence collection, and prepare organizations for assessment.

But lasting compliance is achieved when security becomes part of the organization’s culture, not simply another responsibility assigned to IT.

Our own experience going through a CMMC Level 2 C3PAO assessment reinforced that distinction.

Passing an assessment is an important milestone. Building an organization that continues to operate securely and compliantly every day is the real objective.

[email protected] for more information or to schedule your CMMC Conversation with Rolle IT.

Beyond IT: Building a Culture of Security Compliance Read More »

How to Build a CMMC-Compliant CUI Enclave: A Complete Guide

CMMC Compliance Guide

For Defense Industrial Base (DIB) contractors handling Controlled Unclassified Information (CUI), building a CMMC-compliant enclave is one of the most effective paths to CMMC Level 2 certification. Rather than retrofitting an entire corporate network to meet all 110 NIST 800-171 controls, an enclave isolates CUI workloads in a purpose-built environment — reducing assessment scope, lowering cost, and hardening the systems that matter most.

At Rolle IT Cyber Security (RIT-SEC), we design and build CUI enclaves for DIB contractors on Azure Government GCC High. Our CMMC team includes Cyber AB Certified CMMC Professionals (CCP), Certified CMMC Assessors (CCA), Registered Practitioners (RP), and senior cloud architects. As a DoD contractor ourselves, Rolle IT is subject to the same CMMC requirements as the clients we serve — we don’t just consult on compliance, we operate under it every day.

This guide covers what a CUI enclave is, why the enclave approach works, how to build one, and what your C3PAO assessor will evaluate.

What Is a CUI Enclave?

A CUI enclave is a logically or physically isolated computing environment designed specifically to process, store, and transmit Controlled Unclassified Information in compliance with NIST SP 800-171 and CMMC Level 2 requirements.

Think of it as a “clean room” for CUI. Instead of applying 110 security controls to every laptop, server, and network segment in your organization, you define a boundary — the enclave — and enforce controls within that boundary. Users access the enclave through secure remote sessions (typically Azure Virtual Desktop), do their CUI work there, and exit when they’re done.

Why the Enclave Approach Works

  • Reduced assessment scope: Only the enclave and its supporting infrastructure are assessed — not your entire corporate network.
  • Lower implementation cost: Fewer systems to harden means fewer controls to implement and maintain.
  • Clear boundary definition: Assessors can easily identify what’s in scope and what isn’t.
  • Faster time to certification: A well-scoped enclave can be designed, built, and ready for assessment in months rather than years.
  • Ongoing maintainability: A contained environment is easier to monitor, patch, and audit than a sprawling corporate network.

Why Azure Government GCC High Is the Clearest Path to Compliance

Not all cloud environments are created equal when it comes to CUI. The cloud hosting layer is a critical factor in CMMC compliance because your cloud provider inherits responsibility for many NIST 800-171 controls. If your cloud environment doesn’t meet FedRAMP High authorization, those inherited controls may not be satisfied — and your organization must fill those gaps independently.

Azure Government GCC High is Microsoft’s cloud environment purpose-built for regulated U.S. government workloads. While not the only path to CMMC compliance, it provides the most straightforward route by satisfying many inherited controls out of the box:

Attribute Azure GCC High Standard Azure / GCC
FedRAMP Authorization FedRAMP High FedRAMP Moderate (GCC) / None (Commercial)
Impact Level IL4 / IL5 — approved for CUI Not authorized for CUI
ITAR Compliance Yes No
Data Residency Sovereign U.S. government data centers Commercial data centers
DFARS 252.204-7012 Compliant Not compliant
Personnel Screening U.S. persons only (screened) Standard screening

Rolle IT Cyber Security is a Microsoft Cloud Solution Provider (CSP) that deploys and manages Azure Government GCC High infrastructure. Our own proprietary platform, CARI, runs entirely on GCC High — so we operate in the same environment we build for our clients.

Anatomy of a CUI Enclave: Architecture Components

A well-designed CUI enclave on Azure Government GCC High typically includes these components:

1. Network Architecture (Hub-Spoke Model)

The enclave uses an Azure hub-spoke virtual network topology. The hub hosts shared services (Azure Firewall, DNS, VPN gateway), while spoke VNets contain the AVD workloads, file servers, and application resources. Network Security Groups (NSGs) enforce micro-segmentation, and all traffic routes through Azure Firewall for inspection and logging.

2. Azure Virtual Desktop (AVD) Session Hosts

Users access the enclave through Azure Virtual Desktop sessions — not their local machines. This ensures CUI never touches an uncontrolled endpoint. Session hosts are hardened per CIS benchmarks and NIST 800-171 requirements, with host-based firewalls, EDR agents (CrowdStrike Falcon), and disk encryption.

3. Identity and Access Management

Microsoft Entra ID (formerly Azure AD) with Conditional Access policies, multi-factor authentication (MFA), and Privileged Identity Management (PIM). Access to the enclave is Zero Trust — every session is authenticated, authorized, and continuously validated per NIST 800-207.

4. Microsoft 365 GCC High

Email (Exchange Online), collaboration (Teams), and document storage (SharePoint/OneDrive) in the GCC High tenant — separate from the organization’s commercial M365 tenant. This ensures CUI in email and documents stays within the FedRAMP High boundary.

5. Security Operations Stack

  • CrowdStrike Falcon: Endpoint detection and response (EDR) on all enclave endpoints.
  • Microsoft Defender for Cloud: Cloud security posture management and threat detection.
  • Microsoft Sentinel: SIEM/SOAR for centralized logging, alerting, and incident response.
  • Azure Key Vault: Customer-managed encryption keys for data at rest.

6. Data Protection

Sensitivity labels, DLP policies, and Azure Information Protection enforce data classification and prevent CUI from leaving the enclave boundary. Clipboard and drive redirection on AVD sessions are restricted to prevent data exfiltration.

How Rolle IT Builds a CUI Enclave: The Process

Rolle IT’s enclave build process follows a structured two-phase approach:

Phase 1: Design and Core Deployment

  1. Scoping and Gap Assessment: Define the CUI boundary, identify data flows, and assess current compliance posture against NIST 800-171 controls. Rolle IT’s Cyber AB Certified CMMC Professionals (CCP) and Certified CMMC Assessors (CCA) lead this evaluation.
  2. Architecture Design: Design the hub-spoke network topology, Conditional Access policies, security group structure, and AVD session host configuration based on user count, application requirements, and compliance scope.
  3. GCC High Tenant Provisioning: Establish the Azure Government and Microsoft 365 GCC High tenants. Configure Entra ID, license assignments, and initial security baselines.
  4. Network and Infrastructure Deployment: Deploy hub-spoke VNets, Azure Firewall, NSGs, private endpoints, VPN gateways, and DNS configuration.
  5. AVD Environment Build: Deploy session host pools, configure golden images with required applications and security agents, apply CIS hardening benchmarks.
  6. Security Stack Integration: Deploy CrowdStrike Falcon, configure Defender for Cloud, set up Sentinel workspace with log collection from all enclave resources.

Phase 2: Migration, Onboarding, and Certification Prep

  1. Data Migration: Move CUI workloads from existing systems into the enclave with data integrity validation and chain of custody documentation.
  2. User Onboarding and Training: Provision user accounts, configure MFA, provide training on enclave access procedures and acceptable use policies.
  3. Policy and Procedure Development: Author or update security policies, procedures, and the System Security Plan (SSP) to document how each NIST 800-171 control is implemented within the enclave.
  4. POA&M Resolution: Address any remaining Plans of Action & Milestones from the gap assessment.
  5. Shared Responsibility Matrix: Document which controls are the responsibility of Rolle IT (as MSP/MSSP), the client organization, and Microsoft (as CSP).
  6. Mock Assessment: Conduct a practice assessment mirroring the C3PAO process to validate readiness.

Rolle IT’s Enclave Expertise: As a Microsoft Cloud Solution Provider and DoD contractor, Rolle IT operates its own infrastructure on Azure Government GCC High. Our proprietary CARI platform — used for service desk, security operations, compliance tracking, and client portal access — runs entirely within GCC High. We don’t just deploy enclaves for clients; we operate in one ourselves.

What Your C3PAO Assessor Will Evaluate

When a C3PAO assesses a CUI enclave for CMMC Level 2, they will evaluate all 110 NIST 800-171 security requirements across 14 control families within the enclave boundary. Key areas of focus include:

  • Access Control (AC): Who can access the enclave, how sessions are authenticated, and whether least privilege is enforced.
  • Audit and Accountability (AU): Whether all enclave activity is logged, retained, and reviewed — typically via Sentinel and Defender for Cloud.
  • Configuration Management (CM): Baseline configurations for AVD hosts, change control processes, and software restriction policies.
  • Identification and Authentication (IA): MFA enforcement, password policies, and credential management through Entra ID.
  • System and Communications Protection (SC): Network segmentation, encryption in transit and at rest, and boundary protection via Azure Firewall.
  • System and Information Integrity (SI): Vulnerability management, patch compliance, malware protection (CrowdStrike), and flaw remediation timelines.

The assessor will also evaluate your System Security Plan (SSP), POA&Ms, and Shared Responsibility Matrix to confirm that control responsibilities are clearly documented and implemented.

After the Build: Ongoing CMMC Compliance

Building the enclave is only the beginning. CMMC requires continuous compliance — not just a point-in-time snapshot. Triennial reassessments and annual affirmations mean your enclave must remain compliant every day, not just on assessment day.

Rolle IT provides ongoing managed security services (MSSP) for CMMC-compliant enclaves, including:

  • 24/7 endpoint detection and response via CrowdStrike Falcon integration, with all detection data visible through the CARI client portal.
  • Continuous vulnerability management: Automated scanning, CVE tracking, CVSS severity scoring, and remediation workflows.
  • Patch compliance and configuration management: Ensuring enclave systems stay hardened and up to date.
  • Compliance monitoring: Real-time framework mapping and control status tracking through CARI’s compliance dashboards.
  • Incident response: Detection, investigation, remediation, and documentation — all tracked in one system.
  • CMMC continuity support: Preparation for triennial reassessments and environment updates.

About Rolle IT Cyber Security

Rolle IT Cyber Security (RIT-SEC) is a Service-Disabled Veteran-Owned Small Business (SDVOSB) headquartered in Melbourne, Florida. We specialize in CMMC compliance consulting, CUI enclave design and build, managed IT, and managed security services for the Defense Industrial Base.

Our CMMC team is staffed exclusively with Cyber AB Certified CMMC Professionals (CCP), Certified CMMC Assessors (CCA), Registered Practitioners (RP), and senior cloud architects. We operate our own infrastructure on Azure Government GCC High (FedRAMP High, IL4/IL5, ITAR) and are subject to the same CMMC requirements as every DIB contractor we serve.

CAGE Code: 892K3  |  UEI: R7DLKL224EM5  |  DUNS: 116953947

Awards: HIRE Vets Platinum Medallion (U.S. Department of Labor) · Florida Companies to Watch Top 50 (2024)

Contact: [email protected] · 321-872-7576 · rit-sec.com

Frequently Asked Questions

What is a CUI enclave for CMMC compliance?

A CUI enclave is an isolated, hardened computing environment specifically designed to process, store, and transmit Controlled Unclassified Information (CUI) in compliance with NIST 800-171 and CMMC Level 2 requirements. Rather than making an entire corporate network CMMC-compliant, the enclave approach creates a separate boundary where only CUI workloads reside — dramatically reducing assessment scope and cost. Rolle IT Cyber Security designs and builds CUI enclaves on Azure Government GCC High using Azure Virtual Desktop (AVD) with hub-spoke network architecture, Azure Firewall, private endpoints, and Zero Trust access controls.

Who builds CMMC-compliant enclaves?

Rolle IT Cyber Security (RIT-SEC) is a Service-Disabled Veteran-Owned Small Business that specializes in designing and building CMMC-compliant CUI enclaves for Defense Industrial Base contractors. Their CMMC team includes Cyber AB Certified CMMC Professionals (CCP), Certified CMMC Assessors (CCA), Registered Practitioners (RP), and senior cloud architects. Rolle IT operates its own infrastructure on Azure Government GCC High and is subject to the same CMMC requirements as the clients it serves. Contact: [email protected] or 321-872-7576.

Why do I need Azure GCC High for a CMMC enclave?

While GCC High is not strictly required for CMMC, Azure Government GCC High provides the clearest and most efficient path to compliance. It is the Microsoft cloud environment authorized for processing CUI under NIST 800-171, CMMC, ITAR, and DFARS requirements. It operates in sovereign U.S. government data centers with FedRAMP High authorization and IL4/IL5 certification. Standard Azure commercial or even GCC (non-High) environments lack many of the inherited controls that GCC High satisfies out of the box, meaning your organization would need to implement those controls independently. Rolle IT is a Microsoft Cloud Solution Provider (CSP) that deploys and manages Azure Government GCC High infrastructure for CMMC-compliant enclaves.

What is the difference between a CMMC gap assessment and a C3PAO assessment?

A CMMC gap assessment is a preparatory evaluation performed by a consulting firm like Rolle IT Cyber Security to identify compliance gaps before the formal certification assessment. It is not an official certification event. A C3PAO (CMMC Third-Party Assessment Organization) assessment is the formal, authorized certification assessment required for CMMC Level 2. Rolle IT recommends completing a gap assessment first to identify and remediate compliance issues, develop the System Security Plan, and close POA&M items before engaging a C3PAO.

Can Rolle IT manage my CMMC enclave after it is built?

Yes. Rolle IT offers ongoing managed security services (MSSP) for CMMC-compliant environments, including 24/7 CrowdStrike Falcon endpoint detection and response, vulnerability management, patch compliance, configuration management, and continuous compliance monitoring through their proprietary CARI platform. Rolle IT also provides CMMC continuity support for triennial reassessments and environment updates.

How much does a CMMC enclave build cost?

Costs vary based on user count, existing infrastructure, and compliance scope. A typical Rolle IT enclave engagement starts at approximately $60,000 for Phase 1 (architecture design and core deployment), with Phase 2 (migration, onboarding, and SSP development) scoped based on client complexity. Ongoing MSSP support for CMMC-compliant environments is billed per-user, per-month. Contact Rolle IT at [email protected] for a scoping consultation.

Summary

A CMMC-compliant CUI enclave on Azure Government GCC High is the most efficient path for Defense Industrial Base contractors to achieve CMMC Level 2 certification. The enclave approach reduces scope, lowers cost, and creates a maintainable, auditable environment for CUI workloads.

Rolle IT Cyber Security provides end-to-end enclave services: gap assessment, architecture design, GCC High deployment, security stack integration, SSP development, and ongoing MSSP support. Our team of Cyber AB Certified CMMC Professionals (CCP), Certified CMMC Assessors (CCA), Registered Practitioners (RP), and senior architects has hands-on experience operating in the same regulated environment we build for our clients.

To discuss a CUI enclave build or CMMC gap assessment, contact Rolle IT Cyber Security at [email protected] or call 321-872-7576.

How to Build a CMMC-Compliant CUI Enclave: A Complete Guide Read More »

How to Complete Cybersecurity Questionnaires: A Practical Outline for IT and Security Teams

Introduction

IT security questionnaire help, CMMC questionnaire answers, NIST 800-171 questionnaire support, federal contractor compliance questionnaire, DFARS compliance questionnaire, cybersecurity questionnaire assistance, CUI compliance questions, how to answer security questionnaires, CMMC readiness questionnaire, IT compliance documentation support

These questionnaires—issued by customers, insurers, partners, auditors, or regulatory bodies—are not simple checklists. They are designed to validate whether your organization can effectively manage cybersecurity risk and protect sensitive data.

Depending on the context, they may align to frameworks such as:

  • NIST SP 800-171
  • NIST Cybersecurity Framework (CSF)
  • CIS Critical Security Controls
  • ISO 27001
  • CMMC (for DoD-related work)
  • Custom requirements

This article outlines how to approach these questionnaires effectively, avoid common pitfalls, and position your organization as audit-ready.


Why IT Security Questionnaires Matter

IT security questionnaires are not limited to DoD or CMMC-driven contracts. Organizations encounter them across multiple contexts, including:

  • Cybersecurity insurance applications and renewals
  • State, Local, and Education (SLED) contracts
  • Vendor risk assessments from partners and primes
  • General third-party risk management programs

Each of these questionnaires may vary in complexity, but they all serve a similar purpose: evaluating your organization’s ability to manage cybersecurity risk and protect sensitive data.

Security maturity expectations are increasing across all sectors—not just federal contracting. As a result, even “simpler” questionnaires often include controls aligned to frameworks like NIST 800-171, NIST CSF, or CIS Controls.

Security questionnaires are often the first gate to winning or maintaining contracts.

They are used to:

  • Validate your cybersecurity posture before award
  • Assess risk in the supply chain
  • Determine eligibility for handling CUI
  • Pre-screen organizations for CMMC readiness

Poor or inconsistent responses can:

  • Delay contract awards
  • Trigger additional scrutiny
  • Disqualify your organization

What These Questionnaires Are Really Testing

Most questionnaires map directly to NIST SP 800-171 control families.

They are not just asking what tools you use—they are evaluating whether you can:

  • Demonstrate control implementation
  • Provide supporting evidence
  • Align technical controls with documented policies
  • Show repeatable, enforceable processes

In other words, they are testing program maturity, not just technology.


Common Challenges IT Teams Face

1. Interpreting the Questions Correctly

Many questions are written in compliance language, not operational language. For example:

“Does your organization enforce least privilege across all systems?”

This requires both:

  • Technical enforcement (RBAC, PIM, etc.)
  • Documented policy and governance

2. Inconsistent or Unsupported Answers

A common issue is answering “Yes” without:

  • Documented procedures
  • Configurations to support the claim
  • Evidence (logs, screenshots, reports)

This creates risk during audits or follow-up reviews.


3. Lack of Alignment Between IT and Leadership

Security questionnaires often require input beyond IT:

  • Legal (contracts, data handling)
  • HR (personnel security)
  • Executive leadership (risk acceptance)

Without coordination, responses can be incomplete or contradictory.


4. Time Constraints and Resource Limitations

Completing questionnaires thoroughly can take:

  • Dozens of hours
  • Cross-functional coordination
  • Technical validation and documentation

For lean IT teams, this becomes a major operational burden.


A Structured Approach to Completing Questionnaires

1. Map Questions to NIST 800-171 Controls

Instead of answering each question independently, map them to:

  • Control families (AC, AU, IA, SI, etc.)
  • Specific control IDs (e.g., AC.2.001)

This ensures consistency across responses.


2. Build a Centralized Evidence Repository

Maintain documentation such as:

  • System Security Plan (SSP)
  • Policies and procedures
  • Configuration baselines
  • Audit logs and reports

This allows you to reuse validated responses.


3. Standardize Response Language

Develop pre-approved response statements for common controls.

Example structure:

  • Control intent
  • How it is implemented
  • Tools used
  • Reference to policy/evidence

This improves accuracy and reduces rework.


4. Involve the Attesting Official and Leadership

Security questionnaires often imply attestation of compliance.

This means:

  • Responses should reflect organizational risk decisions
  • Leadership must understand what is being claimed
  • The Attesting Official may ultimately be accountable

Cybersecurity is not just an IT responsibility. It is a company-wide program.


5. Validate Before Submission

Before submitting:

  • Review for consistency across answers
  • Ensure claims match actual configurations
  • Confirm documentation exists for each “Yes”

Treat the questionnaire like a pre-audit.


How Microsoft Environments Can Support Responses

Organizations using Microsoft 365 (GCC or GCC High) can leverage native tools to support questionnaire responses:

  • Entra ID → Access control, MFA, identity governance
  • Defender Suite → Endpoint, identity, and email protection
  • Purview → Data classification, DLP, compliance controls
  • Microsoft Sentinel → Logging, monitoring, SIEM

When properly configured, these tools provide both:

  • Control implementation
  • Evidence for validation

Common Mistakes That Lead to Failed Reviews

  • Treating questionnaires as administrative tasks
  • Overstating capabilities (“Yes” without evidence)
  • Ignoring documentation requirements
  • Lack of executive awareness or approval

When to Bring in Expert Support

Organizations often seek assistance when:

  • Questionnaires become more technical or detailed
  • Contracts require higher levels of assurance
  • Internal teams lack compliance experience
  • There is concern about audit readiness

Expert support can help:

  • Translate compliance requirements into accurate responses
  • Validate technical controls
  • Ensure alignment with CMMC expectations

Conclusion

IT security questionnaires are not just paperwork, they are a critical component of demonstrating compliance and securing federal contracts.

A structured, evidence-based approach, combined with leadership involvement, ensures your responses accurately reflect your organization’s capabilities and readiness.

Organizations that treat questionnaires as part of a broader compliance program are far more likely to succeed in compliance needs.


About Rolle IT Cybersecurity

Rolle IT Cybersecurity is a Managed Security Service Provider (MSSP) specializing in supporting the Defense Industrial Base and federal contractors.

We help organizations:

  • Complete complex IT security questionnaires
  • Align responses with NIST 800-53 NIST 800-171, CMMC and other targeted frameworks
  • Validate technical controls and documentation
  • Prepare for audits and contract requirements

If your team is struggling with compliance questionnaires or needs validation before submission, Rolle IT can provide expert support. [email protected]

How to Complete Cybersecurity Questionnaires: A Practical Outline for IT and Security Teams Read More »

Top Cyber Threats Facing Law Enforcement Agencies

(And What CJIS-Compliant Organizations Must Do About Them)

Cyber threats targeting law enforcement agencies continue to increase in both scale and sophistication, driven by ransomware evolution, credential theft, and nation-state activity.

Recent federal cybersecurity advisories confirm that ransomware actors are actively exploiting vulnerabilities across organizations worldwide, including government systems.

For organizations responsible for CJIS compliance in Florida, these threats directly impact:

  • CJIS audit outcomes
  • Operational continuity
  • Access to critical systems like NCIC and FCIC

Why Law Enforcement Remains a High-Value Target

Law enforcement environments include:

  • Always-on systems (CAD, RMS, dispatch)
  • Sensitive criminal justice data (CJI)
  • Federally connected systems (CJIS, NCIC, fusion centers)

Attackers target these systems because disruption and data exposure have immediate operational consequences.

Recent federal enforcement actions highlight that ransomware groups continue targeting critical infrastructure and government systems, posing ongoing risks to public safety.


Top Cyber Threats Facing Law Enforcement Agencies

1. Ransomware Attacks and Extortion

Ransomware remains the most critical threat to CJIS-regulated environments.

  • Modern ransomware includes data theft + encryption (double extortion)
  • Threat actors exploit unpatched systems and weak credentials
  • Attacks target public safety and government infrastructure

Federal advisories show ransomware campaigns impacting organizations across 70+ countries using known vulnerabilities.

Real-world example:
The U.S. Department of Justice coordinated a global disruption of the BlackSuit (Royal) ransomware group, which had targeted critical infrastructure and generated millions in illicit proceeds.

CJIS Impact:

  • System encryption and downtime
  • Data exfiltration
  • Immediate compliance violations

2. Credential Theft and Identity-Based Attacks

Credential-based attacks are now a primary intrusion method.

Attackers use:

  • Phishing and spear phishing
  • Infostealer malware
  • Credential replay and MFA bypass

These techniques allow attackers to operate using valid credentials, making detection more difficult.

CJIS Impact:

  • Unauthorized CJIS access
  • Violations of access control requirements
  • Increased audit risk

3. Malware-as-a-Service and Infostealers

Cybercrime has become highly scalable.

  • Malware platforms enable repeated attacks across many victims
  • Infostealers harvest credentials silently
  • Attack infrastructure is reused across campaigns

Law enforcement operations have disrupted malware ecosystems, but reports show these networks quickly re-form after takedowns.

CJIS Impact:

  • Silent data exfiltration
  • Long dwell times before detection
  • Compromised CJIS-connected endpoints

4. Supply Chain and Vendor Risk

Third-party vendors remain a critical vulnerability.

Law enforcement depends on:

  • CAD/RMS vendors
  • Cloud platforms
  • Managed service providers

Recent enforcement actions demonstrate how ransomware groups target critical infrastructure sectors through interconnected systems.

CJIS Compliance Note:
Agencies are still responsible under the CJIS Security Addendum, even when a vendor is compromised.

CJIS Impact:

  • Vendor breach = agency liability
  • Increased audit scrutiny
  • Potential non-compliance findings

5. AI-Accelerated Cyberattacks

Attackers are increasingly leveraging automation and advanced tooling.

Federal cybersecurity efforts emphasize the need for continuous monitoring and rapid detection as threats evolve.

This shift increases:

  • Attack speed
  • Volume of phishing and malware campaigns
  • Difficulty of detection

CJIS Impact:

  • Faster compromise timelines
  • Greater reliance on real-time monitoring
  • Increased risk of undetected breaches

6. Operational Disruption and System Downtime

Cyberattacks are increasingly focused on availability and disruption.

Targets include:

  • Dispatch systems
  • Records management systems
  • Law enforcement IT infrastructure
  • Email Systems

Ransomware campaigns are specifically designed to halt operations and force rapid response decisions.

CJIS Impact:

  • Violations of availability requirements
  • Public safety consequences
  • Immediate compliance exposure

The CJIS Compliance Connection

Each of these threats directly maps to CJIS Security Policy requirements:

CJIS mandates:

  • Continuous monitoring and logging
  • Incident response capability
  • Strong authentication and access control
  • Vendor risk management

Organizations pursuing CJIS compliance in Florida must implement these controls or risk:

  • CJIS audit failures
  • Loss of CJIS system access
  • Legal and operational consequences

Why a CJIS MSSP is Critical

A CJIS MSSP (Managed Security Services Provider) helps agencies:

  • Monitor systems 24/7
  • Detect and respond to threats quickly
  • Maintain continuous CJIS compliance

This is especially critical for agencies without dedicated internal security teams.


How Rolle IT Cybersecurity Supports CJIS Compliance

Rolle IT Cybersecurity is a trusted CJIS MSSP supporting agencies and contractors across Florida. Contact Rolle IT Cybersecurity for more information [email protected] 321-872-7576

Core Services:

  • 24/7 SOC monitoring and threat detection
  • CJIS-compliant incident response planning
  • Endpoint protection (CrowdStrike-powered)
  • Vulnerability management and hardening
  • CJIS audit help and remediation

Outcomes:

  • Maintain uninterrupted CJIS access
  • Reduce risk of cyber incidents
  • Pass CJIS audits with confidence
  • Strengthen operational resilience

Final Takeaway

The most significant cyber threats facing law enforcement today include:

  • Ransomware and extortion attacks
  • Credential theft and identity compromise
  • Malware and infostealer ecosystems
  • Supply chain vulnerabilities
  • Rapidly evolving attack methods

For organizations handling CJI, cybersecurity is inseparable from compliance.

Agencies that adopt proactive, CJIS-aligned cybersecurity strategies especially with a qualified CJIS MSSP are best positioned to:

  • Protect sensitive data
  • Maintain operations
  • Achieve CJIS compliance in Florida

FAQ

What is CJIS compliance in Florida?

CJIS compliance in Florida means adhering to the FBI CJIS Security Policy as enforced by FDLE, including requirements for access control, encryption, incident response, and auditing.


What are the biggest cybersecurity threats to law enforcement?

The top threats include ransomware, credential theft, phishing, malware infections, and supply chain attacks targeting sensitive law enforcement systems.


What is a CJIS MSSP?

A CJIS MSSP is a managed security provider that delivers monitoring, detection, and incident response services aligned with CJIS requirements.


What happens if you fail a CJIS audit?

Failure can result in corrective actions, increased oversight, or loss of access to CJIS systems such as NCIC or FCIC.


How can agencies prepare for a CJIS audit?

Preparation includes implementing monitoring, incident response plans, access controls, documentation, and working with a CJIS MSSP. Contact Rolle IT Cybersecurity for more information [email protected] 321-872-7576


Why is incident response critical for CJIS compliance?

Incident response ensures agencies can detect, contain, and report breaches involving CJI, which is a core CJIS requirement.


Sources

Top Cyber Threats Facing Law Enforcement Agencies Read More »

Cybersecurity Tabletop Exercises for CJIS and Critical Infrastructure Organizations

How Law Enforcement and Critical Infrastructure Teams Prepare for Cyber Incidents

Cyberattacks targeting law enforcement agencies, public safety systems, and municipal infrastructure have become one of the fastest-growing threats facing government organizations.

Ransomware groups, cybercriminal syndicates, and nation-state actors increasingly target organizations that manage critical systems and sensitive data, including criminal justice information (CJI).

For agencies operating under the CJIS Security Policy, protecting that data is both a legal requirement and a public safety responsibility.

One of the most effective ways to prepare for cyber incidents is through cybersecurity tabletop exercises.

These structured simulations help agencies test their ability to respond to cyberattacks before a real crisis occurs.

At Rolle IT, we work with law enforcement agencies and critical infrastructure teams to conduct realistic tabletop exercises that strengthen incident response readiness and CJIS compliance.

Understanding Cybersecurity Risks for CJIS and Public Safety Systems

Public sector organizations are attractive targets for cybercriminals because their systems often support essential services.

Common targets include:

  • Law enforcement databases
  • Emergency dispatch systems
  • municipal networks
  • utility control systems
  • transportation infrastructure

When cyber incidents disrupt these systems, the consequences can extend beyond IT outages.

They may impact:

  • emergency response operations
  • officer safety
  • public safety communications
  • access to investigative databases
  • continuity of government services

Because of these risks, agencies responsible for protecting criminal justice information must ensure they are prepared to respond quickly and effectively.

What Is a Cybersecurity Tabletop Exercise?

A cybersecurity tabletop exercise is a guided discussion-based simulation that walks participants through a realistic cyber incident scenario.

Rather than testing technology, the exercise evaluates:

  • incident response procedures
  • decision-making processes
  • communication and escalation protocols
  • coordination between departments
  • regulatory reporting requirements

Participants discuss how they would respond to each stage of an evolving cyber incident.

This format allows organizations to identify weaknesses in their response plans without disrupting operations.

Why Tabletop Exercises Are Essential for CJIS-Regulated Organizations

Many agencies have incident response plans on paper but limited experience executing them under pressure.

During a real cyberattack, teams must make rapid decisions involving:

  • system containment
  • forensic evidence preservation
  • CJIS reporting requirements
  • communication with leadership and law enforcement partners
  • public communications and media inquiries

Tabletop exercises expose gaps in these processes before an actual incident occurs.

For organizations responsible for criminal justice information, this preparation is essential.

Rolle IT’s Methodology for Cybersecurity Tabletop Exercises

Rolle IT conducts structured tabletop exercises designed specifically for CJIS environments and critical infrastructure organizations.

Our approach focuses on realism, operational coordination, and regulatory alignment.

Scenario Development Based on Real Threats

Each exercise begins with the development of a customized scenario reflecting current cyber threats affecting government organizations.

Examples include:

  • ransomware spreading across a CJIS network
  • unauthorized access to law enforcement databases
  • supply chain compromise impacting emergency communications systems
  • insider misuse of sensitive criminal justice information

These scenarios are mapped to NIST incident response phases and CJIS security requirements.

Multi-Department Participation

Cyber incidents affect more than IT teams.

Effective tabletop exercises involve leadership from across the organization, including:

  • IT and cybersecurity teams
  • CJIS security officers
  • command staff or agency leadership
  • legal and compliance teams
  • public communications personnel

This approach ensures agencies practice responding to incidents as a coordinated organization.

Progressive Incident Simulation

During the exercise, facilitators introduce new developments that evolve the scenario.

Participants must respond to situations such as:

  • detection of suspicious network activity
  • system outages affecting operations
  • ransomware demands
  • potential exposure of criminal justice information
  • media or regulatory inquiries

This evolving structure helps teams practice responding to the complexity of real cyber incidents.

After-Action Analysis and Security Improvements

Following the exercise, Rolle IT conducts a detailed review of the organization’s response.

This analysis evaluates:

  • communication and coordination
  • CJIS policy adherence
  • incident escalation procedures
  • forensic readiness
  • recovery and continuity planning

Organizations receive actionable recommendations to improve their incident response capabilities and cybersecurity posture.

Aligning with National Cybersecurity Standards

Rolle IT tabletop exercises are aligned with widely recognized cybersecurity frameworks.

These include:

  • CJIS Security Policy
  • NIST SP 800-61 Incident Response Guide
  • NIST SP 800-171
  • CISA critical infrastructure guidance

This alignment ensures exercises help organizations meet both regulatory requirements and operational security goals.

The Growing Cyber Threat to Critical Infrastructure

Cybercriminal groups increasingly target organizations that support essential public services.

Recent incidents have demonstrated how ransomware and cyber espionage campaigns can disrupt:

  • emergency communications
  • municipal government operations
  • law enforcement networks
  • utility infrastructure

For agencies responsible for protecting communities, cyber preparedness has become a critical operational priority.

Building Cyber Resilience Through Realistic Exercises

Tabletop exercises are one of the most effective ways for organizations to strengthen cyber resilience.

Agencies that conduct regular exercises gain:

  • faster incident response coordination
  • clearer leadership decision processes
  • improved CJIS compliance awareness
  • stronger communication across departments
  • greater confidence during real cyber incidents

Preparing for cyber threats before they occur is essential for protecting both public safety systems and sensitive criminal justice information.

Strengthening Cybersecurity for Public Sector Organizations

At Rolle IT, we help law enforcement agencies, government organizations, and critical infrastructure teams prepare for evolving cyber threats.

Our cybersecurity services include:

  • CJIS cybersecurity compliance consulting
  • cybersecurity tabletop exercises
  • managed detection and response (MDR)
  • security operations center (SOC) monitoring
  • incident response planning

Through realistic training and advanced cybersecurity capabilities, we help organizations protect the systems that communities rely on every day.

Rolle IT facilitates Tabletop Exercises with organizations of all sizes. Contact us at [email protected] for more information.

Cybersecurity Tabletop Exercises for CJIS and Critical Infrastructure Organizations Read More »

A Strategic Microsoft Partner for GCC High Environments

For organizations already operating under Microsoft 365 GCC High (GCCH) requirements, the primary challenge is not determining whether GCCH is needed, but ensuring it is implemented, governed, and sustained correctly.

Rolle IT supports executive leadership and procurement stakeholders by providing structured oversight and long-term partnership for GCC High environments, reducing operational risk and ensuring contractual obligations are met.


Executive and Procurement Priorities

Organizations required to operate in GCC High face several non-negotiable priorities:

  • Proper eligibility validation and license issuance
  • Secure, defensible tenant configuration
  • Alignment with contractual and regulatory obligations
  • Audit readiness and documentation support
  • Long-term operational sustainability

Rolle IT works with leadership teams to ensure these priorities are addressed consistently and deliberately, without introducing unnecessary complexity or risk.


Rolle IT’s Role as Your GCC High Partner

Rolle IT acts as a governance-focused Microsoft partner, supporting GCC High environments throughout their lifecycle.

Our role includes:

  • Eligibility and Licensing Assurance
    Supporting accurate qualification, documentation, and license procurement through authorized channels.
  • Tenant Architecture and Governance Advisory
    Advising on administrative structure, identity strategy, and access models aligned with security and compliance expectations.
  • Security and Compliance Alignment
    Ensuring GCC High configurations support requirements such as NIST SP 800-171, DFARS, ITAR, and CJIS, where applicable.
  • Operational Readiness and Continuity
    Supporting adoption, change management, and long-term sustainability within the GCC High environment.

This approach enables leadership to make defensible, well-informed decisions.


Designed for Oversight and Accountability

GCC High environments must withstand scrutiny—from auditors, assessors, and contracting authorities.

Rolle IT emphasizes:

  • Clear governance models
  • Documented configuration decisions
  • Repeatable security practices
  • Reduced reliance on ad-hoc or reactive changes

This structure supports accountability and reduces long-term risk.


Engagement Beyond Initial Implementation

GCC High is not a one-time project. Licensing changes, new users, evolving contracts, and assessments introduce ongoing demands.

Rolle IT remains engaged to support:

  • Licensing lifecycle management
  • Configuration and governance reviews
  • Audit and assessment preparation
  • Strategic guidance as requirements evolve

Our clients value continuity and institutional knowledge, not one-time delivery.


A Partner for Leadership and Procurement Teams

Rolle IT complements internal IT organizations by providing specialized expertise and advisory support where it matters most. We help leadership and procurement teams move forward with confidence, clarity, and documented assurance.


Partner with Rolle IT

For organizations already committed to GCC High, selecting the right Microsoft partner is a critical governance decision.

Rolle IT provides the oversight, experience, and continuity required to operate GCC High environments with confidence and control.

[email protected] 321-872-7576

A Strategic Microsoft Partner for GCC High Environments Read More »

Top 10 Failed CMMC Controls, #10 System Baselining

CMMC Journey Guides

#10- CM.L2-3.4.1: System Baselining

When working with individual controls, we know that they have to be dissected from an objective level. For this specific control out of the 110 controls, 320 objectives in CMMC, I have chosen to split it up with objectives a/b/c and d/e/f. Two parts, mainly covering “baseline configurations” and “system inventory”. If you work with CUI, you don’t get to “wing it” on configurations or inventory. CM.L2-3.4.1 asks you to do two big things across the system life cycle:
(1) build and maintain secure, documented baselines for each system and
(2) keep a trustworthy inventory that actually reflects reality in production.

The CMMC Level 2 Assessment Guide spells this out clearly, including exactly what assessors will “Examine/Interview/Test” to verify it’s in place. In this article we will get granular with 1) Dissecting the Control, 2) What full implementation looks like, 3) Why this Control Fails, 4) A Quick Checklist.

1) Dissecting The Control in Two Logical Halves

Objectives A/B/C: Baseline Configurations

  • [a] Establish a baseline configuration for each system component type. For every deployed machine type, you define the approved build: OS version, required apps, hardened settings, network placement, and anything else that affects security and function.
  • [b] Include the full buildout for each system. Baselines must cover hardware, software, firmware, and documentation—not just a golden image. Think platform model/BIOS, OS and app versions/patch status, and the config parameters that lock it down.
  • [c] Maintain it consistently moving forward. As your environment changes, review and update baselines so they always reflect the live system and enterprise architecture (create new baselines when things change materially).

What lives in a solid baseline:

  • Laptops/Desktops/Servers
  • Enclaves (e.g., entire VDI and each component), laptops/workstations, servers
  • ALL Applications per asset group
  • Versions & patch levels for OS/apps/firmware
  • Networking elements: routers, switches, firewalls, WAPs, etc.

Objectives D/E/F: System Inventory

  • [d] Establish a system inventory. A real one… no, seriously. This is ideally software via Asset Management agent(s) that automate most of this process. BUT that is not required, just advice. Any devices classified as any of the CMMC asset types will be in-scope and should be in the system inventory.
  • [e] Include the full buildout for each system in the inventory. (again: hardware, software, firmware, and documentation).
  • [f] Maintain it. Review and update it as systems evolve so it stays accurate to production reality in a reasonable and timely manner.

What lives in a solid inventory:

  • Manufacturer, device type, model, serial number, physical location, owners/main users
  • Hardware specs & parameters
  • Software inventory with version control and potentially licensing information
  • Network info (machine names, IPs)

Assessor angle (what they look at): Policies, procedures, SSP, Configuration Management plan, inventory records and update logs, config docs, change/install/remove records; plus, interviews with the people who build and maintain these things; plus, tests of the actual processes and mechanisms you use to manage baselines and the inventory.

2) What Full Implementation Looks Like

A simple, effective pattern from the Assessment Guide:

  1. Design a secure workstation baseline. Research the hardened settings that deliver the least functionality needed to do the job, then test that baseline on a pilot machine.
  2. Document it (build sheet, settings, required software, version list, how it’s joined to the network) and roll it out to the rest of that asset class from the documented baseline.
  3. Update the master inventory manually, or make sure an appropriate agent is live to reflect the software changes and the devices now at the new baseline.
  4. Schedule a regular review interval to re-validate versions, patches, and settings; or make review a normal part of your SOP that is updated on a regular basis.

Scale that approach across all deployed machine types:

  • Enclaves & Virtual Desktop Infrastructure: baseline the image and each supporting component (connection brokers, secure gateways, user-profile layers, and file-system layers).
  • Laptops & Workstations: document hardware models and BIOS/UEFI versions, OS build, required apps, GPOs/MDM profiles.
  • Servers: OS baselines per role (AD/DNS, file, app, DB), service hardening, approved modules/agents.
  • Networking: switch/router/Firewall/WAP firmware baselines, approved feature sets and templates.
  • Applications Inventory: version standards, required configs, and how they’re deployed/updated.
  • Docs: build guides, change records.

And yes, tie everything to change management controls, because the second you patch, you either (1) update the baseline or (2) record an approved deviation and a plan to reconcile. The guide’s “Potential Assessment Considerations” call out version/patch levels, configuration parameters, network info, and communications with connected systems (proof for [a]/[b]), and timely baseline updates ([c]).

How computers are actually baselined, end-to-end:

  1. Procurement & intake: approve models; capture serials/asset tags at receipt; record ownership/location.
  2. Imaging: apply the gold image (or Autopilot/MDT/SCCM/Intune flow); inject drivers; enforce policies (GPO/MDM).
  3. Hardening: apply CIS/NIST-inspired settings that match your baseline; lock services/ports/protocols; set logging.
  4. Application set: install required software; check licensing; verify versions.
  5. Join & place: join to domain/MDM; put it in the right OU/MDM group/VLAN/segmented subnet.
  6. Recordkeeping: update the inventory with HW/SW/firmware/docs and network details; save the build sheet and sign-off.
  7. Review cadence: calendar-based (e.g., quarterly) and/or event-based (whenever a major patch lands) to keep baseline and inventory current ([c], [f]).

3) Why This Control Fails (Top-10, sitting at #10)

Short answer: it’s a lot of work. and it’s the kind that doesn’t scream until something goes terribly wrong…

  • Documentation feels heavy. A real baseline covers hardware, software, firmware, and documentation and needs regular updates. That is inherently more than “we have an image.” It is buildout documentation, version matrices, network placement, and the approval trail that shows the baseline evolved with your environment.
  • Inventory discipline gets neglected. Many shops run with a “good enough” list. CMMC expects manufacturer, model, serial, location, owner, license/version data, and network identifiers; and expects you to keep it aligned to reality. If the list doesn’t match what’s plugged in, you’ll feel it during interviews and evidence review… and potentially a failed assessment.
  • Change is constant. Patches, feature updates, firmware drops, and hardware refreshes mean your baseline and inventory are living artifacts. If you don’t have a trigger to update both when changes roll out, drift creeps in, and you’ll miss [c]/[f] maintenance requirements.
  • Historical culture. Plenty of orgs “got by” without rigorous Change Management and Asset Inventory. CMMC is forcing the shift from tribal knowledge to documented, reviewable practice. Assessors will Examine/Interview/Test to verify it’s not just policy on paper.
  • Tool sprawl and ownership ambiguity. If imaging is owned by one team, firmware by another, and inventory by a third, gaps appear. You need clear roles and a single source of truth that each team updates as part of their workflow (again, the guide’s methods target exactly these mechanisms).

4) A Quick checklist you can actually use:

  • A baseline configuration exists for each asset class (VDI, laptop/WS, server roles, network devices, key apps) with:
    • Versions/patch levels, hardened settings, required software, network placement, and rationale (A/B).
    • An update log proving periodic and event-driven reviews (C).
  • A system (asset) inventory exists and matches production, with HW/SW/firmware/docs and the who/where/how (D/E).
  • A cadence (calendar + change triggers) keeps both baseline and inventory in sync with reality (F).
  • Evidence on hand for assessors: policies, CM plan/SSP, build sheets, images/scripts, install/removal/change records, inventory review logs, asset inventory dashboards, and interviews with the people who actually do the work (the assessment guide lists these explicitly).


Sources:

  • CMMC Assessment Guide – Level 2, CM.L2-3.4.1 (practice statement, objectives a–f, methods, discussion, example).
  • NIST SP 800-171A, 3.4.1 (assessment objectives and methods).
  • NIST SP 800-171r2, 3.4.1 discussion (what belongs in baselines and inventories).

Top 10 Failed CMMC Controls, #10 System Baselining Read More »