RMF / ATO
Security Baseline
A security baseline provides a starting control set that must be related to the system, information and responsible organization. The practical work is understanding applicability, parameters, shared services and the evidence needed to explain the selected safeguards.
How the work is approached
- Confirm the baseline expected by the system owner
- Record tailoring, parameters and inherited-control coverage
- Map controls to implementation owners and evidence sources
An agreed baseline reduces conflicting assumptions between engineering, documentation and assessment teams. It provides a stable reference for tracking implementation and changes. The review should retain baseline and applicability register so the team can explain the decisions later.
Useful starting information
- System categorization and owner direction
- Applicable control catalogs and overlays
- Provider and common-control descriptions
Outputs to agree and review
- Baseline and applicability register
- Tailoring and parameter decisions
- Control ownership and evidence map
A practical example
An organization-required parameter differs from a product default. The team records the expected value, identifies the configuring role and checks the deployed setting against that decision.
What to watch for
The newest catalog release is not automatically the applicable baseline for every contract or authorization. Confirm the governing direction.
Scope, ownership and acceptance criteria should be agreed for the actual environment. The example describes a planning approach, not a promised result or a determination of compliance.
Planning worksheet
Use this short worksheet to record your starting information, action owners and evidence locations before a detailed review.
Download the Security Baseline worksheet (CSV)Continue within this service
Framework reference
NIST RMF publication. Use the baseline and direction applicable to your environment and engagement.
