NIST SP 800-171 · DoD Assessment Methodology · DFARS 252.204-7019 / 7020

Your SPRS score, before the government computes it for you.

All 110 requirements, scored exactly the way DoD scores them: start at 110, subtract 5, 3, or 1 for each requirement not met. The number updates as you go. Nothing leaves your browser until you ask for your results package.

For any company holding, or bidding on, a contract with DFARS 252.204-7012 in it — primes and subs alike — and for any business that wants to be measured against a real standard.

Household · small businessThe BLACKBOOK Self-Assessment104 controls, 0/1/2 scoring, an hour. No government standard, no CUI. Defense contractor · any businessNIST 800-171 / SPRS Self-Assessment110 requirements, DoD point values, the score you would post to SPRS. You are here.

How DoD scores it

110 to start. Every requirement not implemented subtracts its value: 5 for the ones whose absence leaves the network exposed, 3 for partial exposure, 1 for the rest. Lowest possible score is −203.

Two partial credits only. MFA (3.5.3) covering privileged and remote users but not everyone: −3 instead of −5. Encryption in place but not FIPS-validated (3.13.11): −3 instead of −5. Nothing else is partial.

A plan is not a point. A requirement on a POA&M still deducts its full value until it is done. And with no system security plan (3.12.4) the methodology says the assessment cannot be completed at all.

Policy — a formal, approved, written policy says you do it. Approved means signed or otherwise adopted by someone who can bind the company.

Tested SOP — a written procedure implements the policy, and it has been run and shown to work, not just written.

Evidence — you can produce the logs, screenshots, tickets, or records that prove the procedure runs. A requirement is Met only when all three are yes. Anything less is the full deduction; the DoD methodology has no half-credit for good intentions.

110 of 110 · 0 deducted
0 / 110 answered

3.1Access Control

Deductions 0 · 22 requirements
3.1.1
-5
Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems).
Not scored
3.1.2
-5
Limit system access to the types of transactions and functions that authorized users are permitted to execute.
Not scored
3.1.3
-1
Control the flow of CUI in accordance with approved authorizations.
Not scored
3.1.4
-1
Separate the duties of individuals to reduce the risk of malevolent activity without collusion.
Not scored
3.1.5
-3
Employ the principle of least privilege, including for specific security functions and privileged accounts.
Not scored
3.1.6
-1
Use non-privileged accounts or roles when accessing nonsecurity functions.
Not scored
3.1.7
-1
Prevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs.
Not scored
3.1.8
-1
Limit unsuccessful logon attempts.
Not scored
3.1.9
-1
Provide privacy and security notices consistent with applicable CUI rules.
Not scored
3.1.10
-1
Use session lock with pattern-hiding displays to prevent access and viewing of data after a period of inactivity.
Not scored
3.1.11
-1
Terminate (automatically) a user session after a defined condition.
Not scored
3.1.12
-5
Monitor and control remote access sessions.
Not scored
3.1.13
-5
Employ cryptographic mechanisms to protect the confidentiality of remote access sessions.
Not scored
3.1.14
-1
Route remote access via managed access control points.
Not scored
3.1.15
-1
Authorize remote execution of privileged commands and remote access to security-relevant information.
Not scored
3.1.16
-5
Authorize wireless access prior to allowing such connections.
Not scored
3.1.17
-5
Protect wireless access using authentication and encryption.
Not scored
3.1.18
-5
Control connection of mobile devices.
Not scored
3.1.19
-3
Encrypt CUI on mobile devices and mobile computing platforms.
Not scored
3.1.20
-1
Verify and control/limit connections to and use of external systems.
Not scored
3.1.21
-1
Limit use of portable storage devices on external systems.
Not scored
3.1.22
-1
Control CUI posted or processed on publicly accessible systems.
Not scored

3.2Awareness and Training

Deductions 0 · 3 requirements
3.2.1
-5
Ensure that managers, systems administrators, and users are made aware of the security risks associated with their activities and of the applicable policies, standards, and procedures.
Not scored
3.2.2
-5
Ensure that personnel are trained to carry out their assigned information security-related duties and responsibilities.
Not scored
3.2.3
-1
Provide security awareness training on recognizing and reporting potential indicators of insider threat.
Not scored

3.3Audit and Accountability

Deductions 0 · 9 requirements
3.3.1
-5
Create and retain system audit logs and records to the extent needed to enable monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity.
Not scored
3.3.2
-3
Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable.
Not scored
3.3.3
-1
Review and update logged events.
Not scored
3.3.4
-1
Alert in the event of an audit logging process failure.
Not scored
3.3.5
-5
Correlate audit record review, analysis, and reporting processes for investigation and response to indications of unlawful, unauthorized, suspicious, or unusual activity.
Not scored
3.3.6
-1
Provide audit record reduction and report generation to support on-demand analysis and reporting.
Not scored
3.3.7
-1
Provide a system capability that compares and synchronizes internal system clocks with an authoritative source.
Not scored
3.3.8
-1
Protect audit information and audit logging tools from unauthorized access, modification, and deletion.
Not scored
3.3.9
-1
Limit management of audit logging functionality to a subset of privileged users.
Not scored

3.4Configuration Management

Deductions 0 · 9 requirements
3.4.1
-5
Establish and maintain baseline configurations and inventories of organizational systems (hardware, software, firmware, documentation) throughout the system development life cycle.
Not scored
3.4.2
-5
Establish and enforce security configuration settings for information technology products employed in organizational systems.
Not scored
3.4.3
-1
Track, review, approve or disapprove, and log changes to organizational systems.
Not scored
3.4.4
-1
Analyze the security impact of changes prior to implementation.
Not scored
3.4.5
-5
Define, document, approve, and enforce physical and logical access restrictions associated with changes to organizational systems.
Not scored
3.4.6
-5
Employ the principle of least functionality by configuring organizational systems to provide only essential capabilities.
Not scored
3.4.7
-5
Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services.
Not scored
3.4.8
-5
Apply deny-by-exception (blacklisting) policy to prevent unauthorized software, or deny-all, permit-by-exception (whitelisting) policy to allow authorized software.
Not scored
3.4.9
-1
Control and monitor user-installed software.
Not scored

3.5Identification and Authentication

Deductions 0 · 11 requirements
3.5.1
-5
Identify system users, processes acting on behalf of users, and devices.
Not scored
3.5.2
-5
Authenticate (or verify) the identities of users, processes, or devices as a prerequisite to allowing access to organizational systems.
Not scored
3.5.3
-5
Use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts.Partial = MFA in place for privileged accounts and remote access, but not for general (non-privileged) network access
Coverage
Not scored
3.5.4
-1
Employ replay-resistant authentication mechanisms for network access to privileged and non-privileged accounts.
Not scored
3.5.5
-1
Prevent reuse of identifiers for a defined period.
Not scored
3.5.6
-1
Disable identifiers after a defined period of inactivity.
Not scored
3.5.7
-1
Enforce a minimum password complexity and change of characters when new passwords are created.
Not scored
3.5.8
-1
Prohibit password reuse for a specified number of generations.
Not scored
3.5.9
-1
Allow temporary password use for system logons with an immediate change to a permanent password.
Not scored
3.5.10
-5
Store and transmit only cryptographically-protected passwords.
Not scored
3.5.11
-1
Obscure feedback of authentication information.
Not scored

3.6Incident Response

Deductions 0 · 3 requirements
3.6.1
-5
Establish an operational incident-handling capability that includes preparation, detection, analysis, containment, recovery, and user response activities.
Not scored
3.6.2
-5
Track, document, and report incidents to designated officials and/or authorities both internal and external to the organization.
Not scored
3.6.3
-1
Test the organizational incident response capability.
Not scored

3.7Maintenance

Deductions 0 · 6 requirements
3.7.1
-3
Perform maintenance on organizational systems.
Not scored
3.7.2
-5
Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance.
Not scored
3.7.3
-1
Ensure equipment removed for off-site maintenance is sanitized of any CUI.
Not scored
3.7.4
-3
Check media containing diagnostic and test programs for malicious code before the media are used in organizational systems.
Not scored
3.7.5
-5
Require multifactor authentication to establish nonlocal maintenance sessions via external network connections and terminate such connections when nonlocal maintenance is complete.
Not scored
3.7.6
-1
Supervise the maintenance activities of maintenance personnel without required access authorization.
Not scored

3.8Media Protection

Deductions 0 · 9 requirements
3.8.1
-3
Protect (physically control and securely store) system media containing CUI, both paper and digital.
Not scored
3.8.2
-3
Limit access to CUI on system media to authorized users.
Not scored
3.8.3
-5
Sanitize or destroy system media containing CUI before disposal or release for reuse.
Not scored
3.8.4
-1
Mark media with necessary CUI markings and distribution limitations.
Not scored
3.8.5
-1
Control access to media containing CUI and maintain accountability for media during transport outside of controlled areas.
Not scored
3.8.6
-1
Implement cryptographic mechanisms to protect the confidentiality of CUI stored on digital media during transport unless otherwise protected by alternative physical safeguards.
Not scored
3.8.7
-5
Control the use of removable media on system components.
Not scored
3.8.8
-3
Prohibit the use of portable storage devices when such devices have no identifiable owner.
Not scored
3.8.9
-1
Protect the confidentiality of backup CUI at storage locations.
Not scored

3.9Personnel Security

Deductions 0 · 2 requirements
3.9.1
-3
Screen individuals prior to authorizing access to organizational systems containing CUI.
Not scored
3.9.2
-5
Ensure that organizational systems containing CUI are protected during and after personnel actions such as terminations and transfers.
Not scored

3.10Physical Protection

Deductions 0 · 6 requirements
3.10.1
-5
Limit physical access to organizational systems, equipment, and the respective operating environments to authorized individuals.
Not scored
3.10.2
-5
Protect and monitor the physical facility and support infrastructure for organizational systems.
Not scored
3.10.3
-1
Escort visitors and monitor visitor activity.
Not scored
3.10.4
-1
Maintain audit logs of physical access.
Not scored
3.10.5
-1
Control and manage physical access devices.
Not scored
3.10.6
-1
Enforce safeguarding measures for CUI at alternate work sites.
Not scored

3.11Risk Assessment

Deductions 0 · 3 requirements
3.11.1
-3
Periodically assess the risk to organizational operations, assets, and individuals resulting from the operation of organizational systems and the associated processing, storage, or transmission of CUI.
Not scored
3.11.2
-5
Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting those systems and applications are identified.
Not scored
3.11.3
-1
Remediate vulnerabilities in accordance with risk assessments.
Not scored

3.12Security Assessment

Deductions 0 · 4 requirements
3.12.1
-5
Periodically assess the security controls in organizational systems to determine if the controls are effective in their application.
Not scored
3.12.2
-3
Develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems.
Not scored
3.12.3
-5
Monitor security controls on an ongoing basis to ensure the continued effectiveness of the controls.
Not scored
3.12.4
gate
Develop, 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.No system security plan: the DoD methodology treats the assessment as not scorable until one exists.
Not scored

3.13System and Communications Protection

Deductions 0 · 16 requirements
3.13.1
-5
Monitor, control, and protect communications at the external boundaries and key internal boundaries of organizational systems.
Not scored
3.13.2
-5
Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems.
Not scored
3.13.3
-1
Separate user functionality from system management functionality.
Not scored
3.13.4
-1
Prevent unauthorized and unintended information transfer via shared system resources.
Not scored
3.13.5
-5
Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks.
Not scored
3.13.6
-5
Deny network communications traffic by default and allow network communications traffic by exception.
Not scored
3.13.7
-1
Prevent remote devices from simultaneously establishing non-remote connections with organizational systems and communicating via some other connection to resources in external networks (split tunneling).
Not scored
3.13.8
-3
Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards.
Not scored
3.13.9
-1
Terminate network connections associated with communications sessions at the end of the sessions or after a defined period of inactivity.
Not scored
3.13.10
-1
Establish and manage cryptographic keys for cryptography employed in organizational systems.
Not scored
3.13.11
-5
Employ FIPS-validated cryptography when used to protect the confidentiality of CUI.Partial = Encryption is used to protect CUI, but it is not FIPS-validated
Coverage
Not scored
3.13.12
-1
Prohibit remote activation of collaborative computing devices and provide indication of devices in use to users present at the device.
Not scored
3.13.13
-1
Control and monitor the use of mobile code.
Not scored
3.13.14
-1
Control and monitor the use of Voice over Internet Protocol (VoIP) technologies.
Not scored
3.13.15
-5
Protect the authenticity of communications sessions.
Not scored
3.13.16
-1
Protect the confidentiality of CUI at rest.
Not scored

3.14System and Information Integrity

Deductions 0 · 7 requirements
3.14.1
-5
Identify, report, and correct system flaws in a timely manner.
Not scored
3.14.2
-5
Provide protection from malicious code at designated locations within organizational systems.
Not scored
3.14.3
-5
Monitor system security alerts and advisories and take action in response.
Not scored
3.14.4
-5
Update malicious code protection mechanisms when new releases are available.
Not scored
3.14.5
-3
Perform periodic scans of organizational systems and real-time scans of files from external sources as files are downloaded, opened, or executed.
Not scored
3.14.6
-5
Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks.
Not scored
3.14.7
-3
Identify unauthorized use of organizational systems.
Not scored

Your result

Self-assessed — unvalidated

SPRS score: 110

Answer the requirements above. The score, the deductions that drive it, and your plan of action appear here.

Your full results package — every deduction ranked by point value, an auto-built POA&M, and a one-page SPRS-ready summary — is delivered by email to registered readers. Registration takes a minute and carries your answers with it, so the package is yours, not a template.

Something already looks wrong?

Registering means we may email you about your assessment, the BLACKBOOK, and related services; reply "stop" at any time. We do not sell or share your details. Nothing here is a submission to SPRS.