Frameworks / FedRAMP Moderate / SA-1 FedRAMP Moderate
SA - System and Services Acquisition
FedRAMP Moderate SA-1: Policy and Procedures Requires a system and services acquisition policy and supporting procedures to be developed, documented, disseminated, reviewed and updated on a defined cycle.
What else in your programme already covers this This control maps to 37 controls across 18 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
SOC2-CC5.3 COSO principle 12: Deploys control activities through policies and procedures SOC2-CC6.8 Controls to prevent or detect unauthorized or malicious software SOC2-CC7.1 Detection and monitoring procedures for security events are in place SOC2-CC7.2 Monitors system components for anomalies indicating malicious acts SOC2-CC7.3 Evaluates security events to determine incident status 5.24 Information security incident management planning and preparation 5.25 Assessment and decision on information security events 8.15 Logging 8.16 Monitoring activities NIST-CSF-DE.CM-01 Networks and network services are monitored to find potentially adverse events NIST-CSF-DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events NIST-CSF-PR.PS-04 Log records are generated and made available for continuous monitoring NIST-CSF-RS.AN-07 Incident data and metadata are collected, and their integrity and provenance are preserved ASBv3-GS-10 Define and implement DevOps security strategy C5-DEV-01 Policies for the development/procurement of information systems 12.4 Logging and monitoring 12.4 Logging and monitoring 6.9.4 Logging and monitoring 10.2.1 Audit logs enabled on system components Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected .
Other controls in SA - System and Services Acquisition SA-10 Developer Configuration Management SA-11 Developer Testing and Evaluation SA-11(1) Developer Testing and Evaluation | Static Code Analysis. Require the developer of the system, system component, or system service to employ static code analysis tools to identify common flaws and document the results of SA-11(2) Developer Testing and Evaluation | Threat Modeling and Vulnerability Analyses. Require the developer of the system, system component, or system service to perform threat modeling and vulnerability analyses during development and the subsequent testing SA-15 Development Process, Standards, and Tools. a. Require the developer of the system, system component, or system service to follow a documented development process that: 1. Explicitly addresses security and privacy requirements; 2. Identifies the SA-15(3) Development Process, Standards, and Tools | Criticality Analysis. Require the developer of the system, system component, or system service to perform a criticality analysis: (a) At the following decision points in the system development SA-2 Allocation of Resources SA-22 Unsupported System Components. a. Replace system components when support for the components is no longer available from the developer, vendor, or manufacturer; or b. Provide the following options for alternative sources for continued support You are reading one control. How much of FedRAMP Moderate have you already done? FedRAMP Moderate SA-1 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of FedRAMP Moderate your existing evidence covers. Hold ISO 27002:2022 and 182 of 323 FedRAMP Moderate controls already carry evidence.
Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 348 were rejected on the ISO 27002:2022 pair alone.
Query this from an agent The graph holds this control, the 37 it maps to, and the evidence behind each claim, over MCP and REST.