Purchase CMMC or use your DIBBS or SAM Navigator credentials to login
HomeAssessment OverviewAssessment ToolSysten Security PlanSubmit by Email
Submit by Posting in SPRSRegister in PIEE Register in SPRSPurchaseContact Us
Basic Level Self-Assessment Scoring Tool
and System Security Planner
(Based on NIST SP 800-171 Rev 2)

In order to comply with the DoD Cybersecurity Assessment Program, you are required to perform an Assessment of your company’s current compliance with each of the 110 requirements established by NIST. For most businesses, the Basic Level Self-Assessment is all that is required. Higher levels can be sought with certified 3rd party services..

Instructions for the Assessment

  1. Review each of the 110 requirements listed on the Scoring Tool below. In some cases, the intent of the Requirement may not be obvious. Click on the Details link for more information.
  2. NIST and DOD have determined a score value for each Requirement that reflects the relative importance of that particular Requirement.
  3. Each requirement has boxes to the right of the description.
  4. If you comply, click the Implemented box.
  5. If the requirement is something you can do in your business but have not, then click the Not Yet Implemented box.
  6. If the Requirement is something that is not possible with your business, click the Not Applicable box (example, managing cybersecurity between multiple location when your business has only one location).
  7. The Scoring Tool will automatically calculate your score as you go through all Requirements. Your current score will always be shown in the green box on the right side of your screen. This box will also show you how many requirements you have reviewed and scored.
  8. If you need to stop work on the Assessment and pick up at another time where you left off, just click SAVE at the top of the Requirement list and log out of CMMC Navigator. Your work is saved. Alternatively, you can click the Export button to download the assessment tool in Excel format. You can then finish/modify your assessment offline.
  9. If you want to change status for a particular Requirement, just click another box.
  10. When you have completed review of all 110 Requirements you need to click the Export button in the yellow box near the top of this page. This will export your Assessment in Excel file format to your computer. This Excel document will have list all Requirements, your score for each and will provide you with an additional space by each Requirement where you can notes about each score. The Excel file aloows you to make changes in your assessments as needed over time. The Excel document, when it is filled out, is your required System Security Plan (SSP). Click here for further instructions on the SSP.

When you purchase CMMC Navigator, you can use this scoring tool. Click here to get an account.

Export Assessment Score to Excel

  • After you have completed your assessment, be sure to click SAVE.
  • Click the Export button (below) to export your Assessment to an Microsoft Excel spreadsheet.
  • When opening the file you get a warning message "Protected View".
    This is not a problem, just click Enable Editing, then Enable Content, and then the spreadsheet will update.

 then    or 

This function available only with a CMMC Navigator account, a DIBBS Navigator subscription or a SAM Navigator subscription

Assessment Scoring
Starting Score 110
Current Score  
No. Completed of 110
Current score is not final until all 110 requirements have been addressed.>
You must have an account to use this tool. Login here

Para Requirement Value Score  
3.1Access Control  
3.1.1* Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems). Details
3.1.2* Limit system access to the types of transactions and functions that authorized users are permitted to execute. Details
3.1.3 Control the flow of CUI (Controlled Unclassified Information) in accordance with approved authorizations. Details
3.1.4Separate the duties of individuals to reduce the risk of malevolent activity without collusion. Details
3.1.5Employ the principle of least privilege, including for specific security functions and privileged accounts. Details
3.1.6Use non-privileged accounts or roles when accessing non-security functions. Details
3.1.7Prevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs. Details
3.1.8Limit unsuccessful logon attempts. Details
3.1.9Provide privacy and security notices consistent with applicable CUI rules. Details
3.1.10Use session lock with pattern-hiding displays to prevent access and viewing of data after a period of inactivity. Details
3.1.11Terminate (automatically) a user session after a defined condition. Details
3.1.12Monitor and control remote access sessions. Comment: Do not subtract points if remote access not permitted. Details
3.1.13Employ cryptographic mechanisms to protect the confidentiality of remote access sessions. Comment: Do not subtract points if remote access not permitted. Details
3.1.14Route remote access via managed access control points. Details
3.1.15Authorize remote execution of privileged commands and remote access to security- relevant information. Details
3.1.16Authorize wireless access prior to allowing such connections.Comment: Do not subtract points if wireless access not permitted. Details
3.1.17Protect wireless access using authentication and encryption. Comment: Do not subtract points if wireless access not permitted. Details
3.1.18Control connection of mobile devices. Comment: Do not subtract points if connection of mobile devices is not permitted. Details
3.1.19Encrypt CUI on mobile devices and mobile computing platforms. Comment: Exposure limited to CUI on mobile platform. Details
3.1.20* Verify and control/limit connections to and use of external systems. Details
3.1.21Limit use of portable storage devices on external systems. Details
3.1.22* Control CUI posted or processed on publicly accessible systems. Details
3.2Awareness and Training
3.2.1Ensure that managers, systems administrators, and users of organizational systems are made aware of the security risks associated with their activities and of the applicable policies, standards, and procedures related to the security of those systems. Details
3.2.2Ensure that personnel are trained to carry out their assigned information security- related duties and responsibilities. Details
3.2.3Provide security awareness training on recognizing and reporting potential indicators of insider threat. Details
3.3Audit and Accountability
3.3.1Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity. Details
3.3.2Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions. Details
3.3.3Review and update logged events. Details
3.3.4Alert in the event of an audit logging process failure. Details
3.3.5Correlate audit record review, analysis, and reporting processes for investigation and response to indications of unlawful, unauthorized, suspicious, or unusual activity. Details
3.3.6Provide audit record reduction and report generation to support on-demand analysis and reporting. Details
3.3.7Provide a system capability that compares and synchronizes internal system clocks with an authoritative source to generate time stamps for audit records. Details
3.3.8Protect audit information and audit logging tools from unauthorized access, modification, and deletion. Details
3.3.9Limit management of audit logging functionality to a subset of privileged users. Details
3.4Configuration Management
3.4.1Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles. Details
3.4.2Establish and enforce security configuration settings for information technology products employed in organizational systems. Details
3.4.3Track, review, approve or disapprove, and log changes to organizational systems. Details
3.4.4Analyze the security impact of changes prior to implementation. Details
3.4.5Define, document, approve, and enforce physical and logical access restrictions associated with changes to organizational systems. Details
3.4.6Employ the principle of least functionality by configuring organizational systems to provide only essential capabilities. Details
3.4.7Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services. Details
3.4.8Apply deny-by-exception (blacklisting) policy to prevent the use of unauthorized software or deny-all, permit-by-exception (whitelisting) policy to allow the execution of authorized software. Details
3.4.9Control and monitor user-installed software. Details
3.5Identification and Authentication
3.51*.Identify system users, processes acting on behalf of users, and devices. Details
3.52*Authenticate (or verify) the identities of users, processes, or devices, as a prerequisite to allowing access to organizational systems. Details
3.5.3Use multifactor authentication (MFA) for local and network access to privileged accounts and for network access to non-privileged accounts. Comment: Subtract 5 points if MFA not implemented. Subtract 3 points if implemented for remote and privileged users, but not the general user. Details
3.5.4Employ replay-resistant authentication mechanisms for network access to privileged and non-privileged accounts. Details
3.5.5Prevent reuse of identifiers for a defined periods. Details
3.5.6Disable identifiers after a defined period of inactivity. Details
3.5.7Enforce a minimum password complexity and change of characters when new passwords are created. Details
3.5.8Prohibit password reuse for a specified number of generations. Details
3.5.9Allow temporary password use for system logons with an immediate change to a permanent password. Details
3.5.10Store and transmit only cryptographically- protected passwords. =78" DetailsComment: Encrypted representations of passwords include, for example, encrypted versions of passwords and one-way cryptographic hashes of passwords
3.5.11Obscure feedback of authentication information. Details
3.6Incident Response
3.6.1Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, and user response activities. Details
3.6.2Track, document, and report incidents to designated officials and/or authorities both internal and external to the organization. Details
3.6.3Test the organizational incident response capability. Details
3.7.1Perform maintenance on organizational systems. Details
3.7.2Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance. Details
3.7.3Ensure equipment removed for off-site maintenance is sanitized of any CUI. Details
3.7.4Check media containing diagnostic and test programs for malicious code before the media are used in organizational systems. Details
3.7.5Require multifactor authentication to establish nonlocal maintenance sessions via external network connections and terminate such connections when nonlocal maintenance is complete. Details
3.7.6Supervise the maintenance activities of maintenance personnel without required access authorization. Details
3.8Media Protection
3.8.1Protect (i.e., physically control and securely store) system media containing CUI, both paper and digital. Comment: Exposure limited to CUI on media. Details
3.8.2Limit access to CUI on system media to authorized users. Comment: Exposure limited to CUI on media. Details
3.8.3*Sanitize or destroy system media containing CUI before disposal or release for reuse. Comment: While exposure limited to CUI on media, failure to sanitize can result in continual exposure of CUI. Details
3.8.4Mark media with necessary CUI markings and distribution limitations. Details
3.8.5Control access to media containing CUI and maintain accountability for media during transport outside of controlled areas. Details
3.8.6Implement cryptographic mechanisms to protect the confidentiality of CUI stored on digital media during transport unless otherwise protected by alternative physical safeguards. Details
3.8.7Control the use of removable media on system components. Details
3.8.8Prohibit the use of portable storage devices when such devices have no identifiable owner. Details
3.8.9Protect the confidentiality of backup CUI at storage locations. Details
3.9Personnel Security
3.9.1Screen individuals prior to authorizing access to organizational systems containing CUI. Details
3.9.2Ensure that organizational systems containing CUI are protected during and after personnel actions such as terminations and transfers. Details
3.10Physical Protection
3.10.1*Limit physical access to organizational systems, equipment, and the respective operating environments to authorized individuals. Details
3.10.2Protect and monitor the physical facility and support infrastructure for organizational systems. Details
3.10.3*Escort visitors and monitor visitor activity. Details
3.10.4*Maintain audit logs of physical access. Details
3.10.5*Control and manage physical access devices. Details
3.10.6Enforce safeguarding measures for CUI at alternate work sites. Details
3.11Risk Assessment
3.11.1Periodically assess the risk to organizational operations (including mission, functions, image, or reputation), organizational assets, and individuals, resulting from the operation of organizational systems and the associated processing, storage, or transmission of CUI. Details
3.11.2Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting those systems and applications are identified. Details
3.11.3Remediate vulnerabilities in accordance with risk assessments. Details
3.12Security Assessment
3.12.1Periodically assess the security controls in organizational systems to determine if the controls are effective in their application. Details
3.12.2Develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems. Details
3.12.3Monitor security controls on an ongoing basis to ensure the continued effectiveness of the controls. Details
3.12.4Develop, document, and periodically update system security plans that describe system boundaries, system environments of operation, how security requirements are implemented, and the relationships with or connections to other systems. Comment: The absence of a system security plan would result in a finding that an assessment could not be completed due to incomplete information and noncompliance with DFARS clause 252.204-7012. Details
3.13Systems and Communications Protection
3.13.1*Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems. Details
3.13.2Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems. Details
3.13.3Separate user functionality from system management functionality. Details
3.13.4Prevent unauthorized and unintended information transfer via shared system resources. Details
3.13.5*Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks. Details
3.13.6Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception). Details
3.13.7Prevent remote devices from simultaneously establishing non-remote connections with organizational systems and communicating via some other connection to resources in external networks (i.e., split tunneling). Details
3.13.8Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards. Details
3.13.9Terminate network connections associated with communications sessions at the end of the sessions or after a defined period of inactivity. Details
3.13.10Establish and manage cryptographic keys for cryptography employed in organizational systems. Details
3.13.11Employ FIPS-validated cryptography when used to protect the confidentiality of CUI. Comment: Subtract 5 points if no cryptography is employed; 3 points if mostly not FIPS validated. Details
3.13.12Prohibit remote activation of collaborative computing devices and provide indication of devices in use to users present at the device. Details
3.13.13Control and monitor the use of mobile code. Details
3.13.14Control and monitor the use of Voice over Internet Protocol (VoIP) technologies. Details
3.13.15Protect the authenticity of communications sessions. Details
3.13.16Protect the confidentiality of CUI at rest. Details
3.14System and Information Integrity
3.14.1*Identify, report, and correct system flaws in a timely manner. Details
3.14.2*Provide protection from malicious code at designated locations within organizational systems. Details
3.14.3Monitor system security alerts and advisories and take action in response. Details
3.14.4*Update malicious code protection mechanisms when new releases are available. Details
3.14.5*Perform periodic scans of organizational systems and real-time scans of files from external sources as files are downloaded, opened, or executed. Details
3.14.6Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks. Details
3.14.7Identify unauthorized use of organizational systems. Details
©Copyright 2021-2022 DIBBSNav, LLC