SPRS Self-Score Calculator

3.1.1 — Limit system access to authorized users5 pts

Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems).

3.1.2 — Limit access to permitted transactions and functions5 pts

Limit system access to the types of transactions and functions that authorized users are permitted to execute.

3.1.3 — Control the flow of CUI1 pts

Control the flow of CUI in accordance with approved authorizations.

3.1.4 — Separate duties of individuals1 pts

Separate the duties of individuals to reduce the risk of malevolent activity without collusion.

3.1.5 — Least privilege3 pts

Employ the principle of least privilege, including for specific security functions and privileged accounts.

3.1.6 — Non-privileged accounts for non-security functions1 pts

Use non-privileged accounts or roles when accessing non-security functions.

3.1.7 — Prevent privileged function execution by non-privileged users; audit1 pts

Prevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs.

3.1.8 — Limit unsuccessful logon attempts1 pts

Limit unsuccessful logon attempts.

3.1.9 — Privacy and security notices1 pts

Provide privacy and security notices consistent with applicable CUI rules.

3.1.10 — Session lock with pattern-hiding displays1 pts

Use session lock with pattern-hiding displays to prevent access and viewing of data after a period of inactivity.

3.1.11 — Terminate user sessions automatically1 pts

Terminate (automatically) a user session after a defined condition.

3.1.12 — Monitor and control remote access5 pts

Monitor and control remote access sessions.

Do not subtract points if remote access not permitted.

3.1.13 — Cryptographic protection of remote access5 pts

Employ cryptographic mechanisms to protect the confidentiality of remote access sessions.

Do not subtract points if remote access not permitted.

3.1.14 — Route remote access via managed access control points1 pts

Route remote access via managed access control points.

3.1.15 — Authorize remote privileged commands1 pts

Authorize remote execution of privileged commands and remote access to security-relevant information.

3.1.16 — Authorize wireless access5 pts

Authorize wireless access prior to allowing such connections.

Do not subtract points if wireless access not permitted.

3.1.17 — Protect wireless access5 pts

Protect wireless access using authentication and encryption.

Do not subtract points if wireless access not permitted.

3.1.18 — Control connection of mobile devices5 pts

Control connection of mobile devices.

Do not subtract points if connection of mobile devices is not permitted.

3.1.19 — Encrypt CUI on mobile devices3 pts

Encrypt CUI on mobile devices and mobile computing platforms.

3.1.20 — Control connections to external systems1 pts

Verify and control/limit connections to and use of external systems.

3.1.21 — Limit portable storage on external systems1 pts

Limit use of portable storage devices on external systems.

3.1.22 — Control CUI on publicly accessible systems1 pts

Control CUI posted or processed on publicly accessible systems.

3.2.1 — Security awareness for all users5 pts

Ensure 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.

3.2.2 — Role-based security training5 pts

Ensure that personnel are trained to carry out their assigned information security-related duties and responsibilities.

3.2.3 — Insider threat awareness1 pts

Provide security awareness training on recognizing and reporting potential indicators of insider threat.

3.3.1 — Create and retain audit logs5 pts

Create 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.

3.3.2 — Trace actions to individual users3 pts

Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions.

3.3.3 — Review and update logged events1 pts

Review and update logged events.

3.3.4 — Alert on audit logging failure1 pts

Alert in the event of an audit logging process failure.

3.3.5 — Correlate audit review for investigation5 pts

Correlate audit record review, analysis, and reporting processes for investigation and response to indications of unlawful, unauthorized, suspicious, or unusual activity.

3.3.6 — Audit reduction and report generation1 pts

Provide audit record reduction and report generation to support on-demand analysis and reporting.

3.3.7 — Authoritative time source1 pts

Provide a system capability that compares and synchronizes internal system clocks with an authoritative source to generate time stamps for audit records.

3.3.8 — Protect audit information and tools1 pts

Protect audit information and audit logging tools from unauthorized access, modification, and deletion.

3.3.9 — Limit audit management to privileged subset1 pts

Limit management of audit logging functionality to a subset of privileged users.

3.4.1 — Baseline configurations and inventories5 pts

Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles.

3.4.2 — Enforce security configuration settings5 pts

Establish and enforce security configuration settings for information technology products employed in organizational systems.

3.4.3 — Track and approve system changes1 pts

Track, review, approve or disapprove, and log changes to organizational systems.

3.4.4 — Analyze security impact of changes1 pts

Analyze the security impact of changes prior to implementation.

3.4.5 — Access restrictions for changes5 pts

Define, document, approve, and enforce physical and logical access restrictions associated with changes to organizational systems.

3.4.6 — Least functionality5 pts

Employ the principle of least functionality by configuring organizational systems to provide only essential capabilities.

3.4.7 — Restrict nonessential programs, ports, protocols, services5 pts

Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services.

3.4.8 — Application allowlisting / denylisting5 pts

Apply 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.

3.4.9 — Control user-installed software1 pts

Control and monitor user-installed software.

3.5.1 — Identify users, processes, devices5 pts

Identify system users, processes acting on behalf of users, and devices.

3.5.2 — Authenticate users, processes, devices5 pts

Authenticate (or verify) the identities of users, processes, or devices, as a prerequisite to allowing access to organizational systems.

3.5.3 — Multifactor authentication3–5 pts

Use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts.

“Partially” = MFA covers remote and privileged users but not general users (−3 instead of −5).

3.5.4 — Replay-resistant authentication1 pts

Employ replay-resistant authentication mechanisms for network access to privileged and non-privileged accounts.

3.5.5 — Prevent identifier reuse1 pts

Prevent reuse of identifiers for a defined period.

3.5.6 — Disable inactive identifiers1 pts

Disable identifiers after a defined period of inactivity.

3.5.7 — Password complexity1 pts

Enforce a minimum password complexity and change of characters when new passwords are created.

3.5.8 — Prohibit password reuse1 pts

Prohibit password reuse for a specified number of generations.

3.5.9 — Temporary passwords require immediate change1 pts

Allow temporary password use for system logons with an immediate change to a permanent password.

3.5.10 — Cryptographically protect passwords5 pts

Store and transmit only cryptographically-protected passwords.

3.5.11 — Obscure authentication feedback1 pts

Obscure feedback of authentication information.

3.6.1 — Operational incident-handling capability5 pts

Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, and user response activities.

3.6.2 — Track, document, and report incidents5 pts

Track, document, and report incidents to designated officials and/or authorities both internal and external to the organization.

3.6.3 — Test incident response capability1 pts

Test the organizational incident response capability.

3.7.1 — Perform system maintenance3 pts

Perform maintenance on organizational systems.

3.7.2 — Control maintenance tools and personnel5 pts

Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance.

3.7.3 — Sanitize equipment for off-site maintenance1 pts

Ensure equipment removed for off-site maintenance is sanitized of any CUI.

3.7.4 — Check maintenance media for malicious code3 pts

Check media containing diagnostic and test programs for malicious code before the media are used in organizational systems.

3.7.5 — MFA for nonlocal maintenance5 pts

Require multifactor authentication to establish nonlocal maintenance sessions via external network connections and terminate such connections when nonlocal maintenance is complete.

3.7.6 — Supervise unauthorized maintenance personnel1 pts

Supervise the maintenance activities of maintenance personnel without required access authorization.

3.8.1 — Protect system media containing CUI3 pts

Protect (i.e., physically control and securely store) system media containing CUI, both paper and digital.

3.8.2 — Limit access to CUI on media3 pts

Limit access to CUI on system media to authorized users.

3.8.3 — Sanitize media before disposal or reuse5 pts

Sanitize or destroy system media containing CUI before disposal or release for reuse.

3.8.4 — Mark media with CUI markings1 pts

Mark media with necessary CUI markings and distribution limitations.

3.8.5 — Control media during transport1 pts

Control access to media containing CUI and maintain accountability for media during transport outside of controlled areas.

3.8.6 — Encrypt CUI on media in transport1 pts

Implement cryptographic mechanisms to protect the confidentiality of CUI stored on digital media during transport unless otherwise protected by alternative physical safeguards.

3.8.7 — Control removable media5 pts

Control the use of removable media on system components.

3.8.8 — Prohibit ownerless portable storage3 pts

Prohibit the use of portable storage devices when such devices have no identifiable owner.

3.8.9 — Protect backup CUI1 pts

Protect the confidentiality of backup CUI at storage locations.

3.9.1 — Screen individuals before CUI access3 pts

Screen individuals prior to authorizing access to organizational systems containing CUI.

3.9.2 — Protect CUI during personnel actions5 pts

Ensure that organizational systems containing CUI are protected during and after personnel actions such as terminations and transfers.

3.10.1 — Limit physical access5 pts

Limit physical access to organizational systems, equipment, and the respective operating environments to authorized individuals.

3.10.2 — Protect and monitor the facility5 pts

Protect and monitor the physical facility and support infrastructure for organizational systems.

3.10.3 — Escort and monitor visitors1 pts

Escort visitors and monitor visitor activity.

3.10.4 — Maintain physical access audit logs1 pts

Maintain audit logs of physical access.

3.10.5 — Control physical access devices1 pts

Control and manage physical access devices.

3.10.6 — Safeguard CUI at alternate work sites1 pts

Enforce safeguarding measures for CUI at alternate work sites.

3.11.1 — Periodically assess risk3 pts

Periodically 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.

3.11.2 — Scan for vulnerabilities5 pts

Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting those systems and applications are identified.

3.11.3 — Remediate vulnerabilities1 pts

Remediate vulnerabilities in accordance with risk assessments.

3.12.1 — Periodically assess security controls5 pts

Periodically assess the security controls in organizational systems to determine if the controls are effective in their application.

3.12.2 — Plans of action (POA&M)3 pts

Develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems.

3.12.3 — Monitor controls on an ongoing basis5 pts

Monitor security controls on an ongoing basis to ensure the continued effectiveness of the controls.

3.12.4 — System Security Plangating

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.

3.13.1 — Monitor and protect communications at boundaries5 pts

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.

3.13.2 — Secure engineering principles5 pts

Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems.

3.13.3 — Separate user and management functionality1 pts

Separate user functionality from system management functionality.

3.13.4 — Prevent information transfer via shared resources1 pts

Prevent unauthorized and unintended information transfer via shared system resources.

3.13.5 — Subnetworks for publicly accessible components5 pts

Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks.

3.13.6 — Deny-by-default network traffic5 pts

Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception).

3.13.7 — Prevent split tunneling1 pts

Prevent 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).

3.13.8 — Encrypt CUI in transmission3 pts

Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards.

3.13.9 — Terminate network connections1 pts

Terminate network connections associated with communications sessions at the end of the sessions or after a defined period of inactivity.

3.13.10 — Manage cryptographic keys1 pts

Establish and manage cryptographic keys for cryptography employed in organizational systems.

3.13.11 — FIPS-validated cryptography for CUI3–5 pts

Employ FIPS-validated cryptography when used to protect the confidentiality of CUI.

“Partially” = encryption is in place but mostly not FIPS-validated (−3 instead of −5).

3.13.12 — Control collaborative computing devices1 pts

Prohibit remote activation of collaborative computing devices and provide indication of devices in use to users present at the device.

3.13.13 — Control mobile code1 pts

Control and monitor the use of mobile code.

3.13.14 — Control VoIP1 pts

Control and monitor the use of Voice over Internet Protocol (VoIP) technologies.

3.13.15 — Protect authenticity of communications sessions5 pts

Protect the authenticity of communications sessions.

3.13.16 — Protect CUI at rest1 pts

Protect the confidentiality of CUI at rest.

3.14.1 — Identify and correct system flaws5 pts

Identify, report, and correct system flaws in a timely manner.

3.14.2 — Malicious code protection5 pts

Provide protection from malicious code at designated locations within organizational systems.

3.14.3 — Monitor security alerts and advisories5 pts

Monitor system security alerts and advisories and take action in response.

3.14.4 — Update malicious code protection5 pts

Update malicious code protection mechanisms when new releases are available.

3.14.5 — Periodic and real-time scans3 pts

Perform periodic scans of organizational systems and real-time scans of files from external sources as files are downloaded, opened, or executed.

3.14.6 — Monitor systems and traffic for attacks5 pts

Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks.

3.14.7 — Identify unauthorized use3 pts

Identify unauthorized use of organizational systems.