Docs · Last updated 2026-05-26

Compliance mappings

Every one of the 110 NIST 800-171 R2 controls, with an honest status of what Readyline does on its side vs. what the customer owns. Use this table when you write your SSP. Most of the "customer responsibility" rows still need a narrative even though the platform doesn't help.

Status legend

Built-in

40 of 110 controls

Readyline implements without customer action. Cite the platform in your SSP narrative.

Configurable

49 of 110 controls

Platform provides the mechanism; customer enables / configures via the admin console.

Customer

21 of 110 controls

Org / facility / personnel responsibility. Readyline tracks status but does not enforce.

Status assignments are conservative. We only mark a control "built-in" when the platform itself enforces it without customer action. When the platform helps but the customer must enable or configure something, it's "configurable". Physical, personnel, and process controls are "customer". This matches how a C3PAO would assess the same controls.

All 110 controls

Access Control (22 controls)

Control Requirement Status Level
3.1.1

Limit system access to authorized users, processes acting on behalf of users, and devices.

Enforced via login + RBAC.
Built-in L1
3.1.2

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

Permission system gates every action.
Built-in L1
3.1.3

Control the flow of CUI in accordance with approved authorizations.

Configurable L2
3.1.4

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

Configurable L2
3.1.5

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

Configurable L2
3.1.6

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

Configurable L2
3.1.7

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

Configurable L2
3.1.8

Limit unsuccessful logon attempts.

Configurable L2
3.1.9

Provide privacy and security notices consistent with applicable CUI rules.

Configurable L2
3.1.10

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

Configurable L2
3.1.11

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

Configurable L2
3.1.12

Monitor and control remote access sessions.

Configurable L2
3.1.13

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

Configurable L2
3.1.14

Route remote access via managed access control points.

Configurable L2
3.1.15

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

Configurable L2
3.1.16

Authorize wireless access prior to allowing such connections.

Configurable L2
3.1.17

Protect wireless access using authentication and encryption.

Configurable L2
3.1.18

Control connection of mobile devices.

Configurable L2
3.1.19

Encrypt CUI on mobile devices and mobile computing platforms.

Configurable L2
3.1.20

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

Configurable L1
3.1.21

Limit use of organizational portable storage devices on external systems.

Configurable L2
3.1.22

Control CUI posted or processed on publicly accessible systems.

Configurable L1

Awareness and Training (3 controls)

Control Requirement Status Level
3.2.1

Ensure that managers, systems administrators, and users of organizational systems are made aware of the security risks associated with their activities.

Customer L2
3.2.2

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

Customer L2
3.2.3

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

Customer L2

Audit and Accountability (9 controls)

Control Requirement Status Level
3.3.1

Create and retain system audit logs and records to enable monitoring, analysis, investigation, and reporting of unlawful or unauthorized activity.

Central audit log captures all auth + privileged actions.
Built-in L2
3.3.2

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

Per-user audit trail tied to user_id.
Built-in L2
3.3.3

Review and update logged events.

Customer can extend audit categories.
Configurable L2
3.3.4

Alert in the event of an audit logging process failure.

Failure alerts surfaced in console.
Built-in L2
3.3.5

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

Audit review cadence is org policy.
Configurable L2
3.3.6

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

Built-in L2
3.3.7

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

Built-in L2
3.3.8

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

Audit logs append-only, role-restricted.
Built-in L2
3.3.9

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

Audit management gated by admin role.
Built-in L2

Configuration Management (9 controls)

Control Requirement Status Level
3.4.1

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

Configurable L2
3.4.2

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

Configurable L2
3.4.3

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

Configurable L2
3.4.4

Analyze the security impact of changes prior to implementation.

Configurable L2
3.4.5

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

Configurable L2
3.4.6

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

Configurable L2
3.4.7

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

Configurable L2
3.4.8

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.

Configurable L2
3.4.9

Control and monitor user-installed software.

Configurable L2

Identification and Authentication (11 controls)

Control Requirement Status Level
3.5.1

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

Unique user accounts required.
Built-in L1
3.5.2

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

Password + optional MFA at login.
Built-in L1
3.5.3

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

TOTP MFA available; customer enables per user.
Configurable L2
3.5.4

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

Built-in L2
3.5.5

Prevent reuse of identifiers for a defined period.

Built-in L2
3.5.6

Disable identifiers after a defined period of inactivity.

Built-in L2
3.5.7

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

Built-in L2
3.5.8

Prohibit password reuse for a specified number of generations.

Built-in L2
3.5.9

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

Built-in L2
3.5.10

Store and transmit only cryptographically-protected passwords.

Built-in L2
3.5.11

Obscure feedback of authentication information.

Built-in L2

Incident Response (3 controls)

Control Requirement Status Level
3.6.1

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

Configurable L2
3.6.2

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

Configurable L2
3.6.3

Test the organizational incident response capability.

Configurable L2

Maintenance (6 controls)

Control Requirement Status Level
3.7.1

Perform maintenance on organizational systems.

Maintenance scheduling is org process.
Customer L2
3.7.2

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

Maintenance tools/techniques are org process.
Customer L2
3.7.3

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

Customer L2
3.7.4

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

Diagnostic media handling is on-site.
Customer L2
3.7.5

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

MFA for nonlocal maintenance is infra-side.
Customer L2
3.7.6

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

Maintenance personnel supervision.
Customer L2

Media Protection (9 controls)

Control Requirement Status Level
3.8.1

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

Configurable L2
3.8.2

Limit access to CUI on system media to authorized users.

Configurable L2
3.8.3

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

Configurable L1
3.8.4

Mark media with necessary CUI markings and distribution limitations.

Configurable L2
3.8.5

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

Configurable L2
3.8.6

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

Configurable L2
3.8.7

Control the use of removable media on system components.

Configurable L2
3.8.8

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

Configurable L2
3.8.9

Protect the confidentiality of backup CUI at storage locations.

Configurable L2

Personnel Security (2 controls)

Control Requirement Status Level
3.9.1

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

Customer L2
3.9.2

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

Customer L2

Physical Protection (6 controls)

Control Requirement Status Level
3.10.1

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

Physical access limited.
Customer L1
3.10.2

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

Physical safeguards.
Customer L2
3.10.3

Escort visitors and monitor visitor activity.

Escort visitors.
Customer L1
3.10.4

Maintain audit logs of physical access.

Maintain physical access logs.
Customer L1
3.10.5

Control and manage physical access devices.

Control physical access devices.
Customer L1
3.10.6

Enforce safeguarding measures for CUI at alternate work sites.

Alternate work sites.
Customer L2

Risk Assessment (3 controls)

Control Requirement Status Level
3.11.1

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.

Configurable L2
3.11.2

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

Configurable L2
3.11.3

Remediate vulnerabilities in accordance with risk assessments.

Configurable L2

Security Assessment (4 controls)

Control Requirement Status Level
3.12.1

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

Self-assessment workflow built in.
Built-in L2
3.12.2

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

POAM tracking built in.
Built-in L2
3.12.3

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

Control implementation status tracked.
Built-in L2
3.12.4

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.

SSP generation built in.
Built-in L2

System and Communications Protection (16 controls)

Control Requirement Status Level
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.

Web tier behind firewall, app/db on private network.
Built-in L1
3.13.2

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

Defense-in-depth: WAF + app auth + DB ACL.
Built-in L2
3.13.3

Separate user functionality from system management functionality.

Built-in L2
3.13.4

Prevent unauthorized and unintended information transfer via shared system resources.

Built-in L2
3.13.5

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

Public-facing components isolated from CUI tier.
Built-in L1
3.13.6

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

Default-deny firewall policy.
Built-in L2
3.13.7

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

Split tunneling is endpoint policy.
Customer L2
3.13.8

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

TLS 1.2+ enforced for all traffic.
Built-in L2
3.13.9

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

Built-in L2
3.13.10

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

Built-in L2
3.13.11

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

FIPS-validated TLS on supported deploys.
Built-in L2
3.13.12

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

Built-in L2
3.13.13

Control and monitor the use of mobile code.

Built-in L2
3.13.14

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

Built-in L2
3.13.15

Protect the authenticity of communications sessions.

Session-bound CSRF + signed tokens.
Built-in L2
3.13.16

Protect the confidentiality of CUI at rest.

Database + file storage encrypted at rest.
Built-in L2

System and Information Integrity (7 controls)

Control Requirement Status Level
3.14.1

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

Vulnerability info surfaced; customer applies patches.
Configurable L1
3.14.2

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

Endpoint anti-malware is org responsibility.
Customer L1
3.14.3

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

Configurable L2
3.14.4

Update malicious code protection mechanisms when new releases are available.

Anti-malware updates org-managed.
Customer L1
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.

Scans run by customer.
Customer L1
3.14.6

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

System monitoring on infra side.
Built-in L2
3.14.7

Identify unauthorized use of organizational systems.

Unauthorized use flagged by audit log.
Built-in L2

OSCAL export

For programs that consume OSCAL (the NIST Open Security Controls Assessment Language), Readyline can export your SSP and POAM in OSCAL JSON. Use the CLI php artisan tenant:export --format=oscal or the admin console export button.

Rev 3 readiness

Readyline currently maps to NIST 800-171 R2 (110 controls). NIST 800-171 R3 (97 controls + Organization-Defined Parameters) is on the roadmap; see the Rev 3 blog post for what's changing and when we plan to ship the R3 catalog.