The Secure Controls Framework Council (SCF Council) is very pleased to highlight another successful implementation of the Secure Controls Framework (SCF) for NIST 800-171 implementation that resulted in a Cybersecurity Maturity Model Certification(CMMC) Level 2 certification.
Logos Systems, a Texas-based Managed Security Service Provider (MSSP) and vCISO firm, serves defense contractors and other regulated organizations that handle Controlled Unclassified Information (CUI).
What Logos Did With The SCF
Logos used the SCF as the control language, where it created a Service Standard organized by SCF domain and control ID. For each control it says what the control means as a managed service, in Logos's service vocabulary.
Why The SCF Fit Logos' Needs
- Efficiency. One set of control IDs is shared by the client, the provider and the assessor, and the NIST 800-171 mapping comes with the SCF.
- Evidence Request List (ERL). Mapping client evidence to the SCF’s ERL cuts duplicate artifact requests across clients and frameworks.
- Established Models. Risk, maturity and program management use SCF models (SCR-RMM, SCR-CMM, SCRMS) instead of separate methods.
- Unified Scoping Guide (USG). The USG gives one scoping method, so the same asset tags drive baseline configurations and vulnerability and patch management.
- Scalability. Adding another framework later (for example SOC 2 or HIPAA readiness) extends the same control set instead of starting a second program.
Logos did not have to build a crosswalk, since the SCF already maps each control to the NIST 800-171 R2 requirements and NIST 800-171A Assessment Objectives (AOs) it supports, so the assessor's lens and the delivery team's language stay linked.
William Birchett, CEO, Logos Systems:
"NIST 800-171 tells you what has to be true. The SCF gives you one place to organize how you make it true, and we use all of it: the control set and its 800-171 mapping, the risk and maturity models, the management system, the scoping guide, and the evidence request list. We wrote down what each control means as a service we deliver. That standard drives our shared responsibility matrix, and each control's cadence became checklists the team works from. That's how the assessor's objectives and our daily work stay the same thing."
The Results: CMMC L2 Certification
Logos Systems was assessed by an independent C3PAO against NIST SP 800-171 for CMMC Level 2, with a final outcome of 110 of 110 and no POA&M. Multiple Logos clients have also passed independent C3PAO Level 2 assessments with no POA&M.
One control language runs through policy, delivery, tickets and evidence. Logos ran the whole program on the full SCF GRC toolkit, not just the control list:
- Secure, Compliant & Resilient Risk Management Model (SCR-RMM) was used to perform the risk assessment (RA)controls.
- Secure, Compliant & Resilient Capability Maturity Model (SCR-CMM) was used to evaluate control maturity, including planned failure for controls.
- Secure, Compliant & Resilient Management System (SCRMS) was used to run the whole program and practice.
- Unified Scoping Guide (USG) was used to scope environments and to tag assets in the baseline configurations and in the vulnerability and patch management program.
- SCF Evidence Request List (ERL) was used for evidence mapping, so one artifact serves many requests and artifact gathering is not repeated.
- Turned control cadence into checklists. Each control's cadence became recurring checklist tasks, and requests or incidents get checklists by ticket type. Each checklist lists the 800-171 objectives it evidences.
- Used the Service Standard to drive the Shared Responsibility Matrix (SRM). Due to how each SCF control already states what Logos does as a service, the SRM follows from it by NIST 800-171 AO to show what Logos covers for a client and what the client keeps.
- Documented the system. The System Security Plan(SSP) describes the Logos CUI Enclave and cites the standards and the SRM.