SC-39 Process Isolationsc-39
Whether an AWS call fetches evidence for this control, and what to run. Its Rev5 baselines, the indicators that reach it and the FedRAMP guidance attached to it open below.
Nothing names itNo recipe names SC-39. 17 reach an indicator it shares, which is adjacency and not coverage — worth reading, not worth recording as evidence for this control.
Collect evidence (0)
Authored AWS recipes whose output is evidence for SC-39. This mapping is this project’s opinion (overlay v3.0.0), versioned separately from the dataset — the upstream FedRAMP rules name none of these tools.
No authored recipe names SC-39. The nearest authored work is below.
A separate execution domain per process is a property of the Nitro hypervisor and the guest operating system, not a setting anyone can query. A 3PAO reads AWS's own FedRAMP authorization package for the hypervisor boundary and your architecture description for the guest side; no customer-invocable API reports process isolation.
This project’s assessment (automation register v0.9.0, reviewed 2026-08-04), versioned separately from the dataset and from the evidence overlays. It is an opinion about the AWS surface on that date, and the surface moves.
The KSIs that reach it are KSI-IAM-ELP, KSI-IAM-JIT, KSI-SVC-EIS — which is what asks for it. The evidence it asks for is written, not fetched. Browse /collect for the whole authored corpus.
Reaches the same indicator, not SC-39
These recipes prove a KSI that reaches it. None of them claims SC-39 — treat them as neighbours worth reading, not as coverage.
- Account-wide credential report proving MFA is active per principal and that passwords/access keys are rotated within policy via KSI-IAM-ELP
- Full snapshot of every IAM user, group, role, and attached/inline policy with their relationships, used to review that granted permissions match least-privilege intent via KSI-IAM-ELP
- Active unused-access findings identifying IAM roles, access keys, console passwords, and service/action-level permissions that have not been used within the configured age, driving right-sizing and removal via KSI-IAM-ELP KSI-IAM-JIT
- AWS Config compliance result proving no customer-managed IAM policy grants full administrative access (Allow Action:* on Resource:*) via KSI-IAM-ELP
- How operators actually reach the environment from outside it: the managed access paths that exist, the logging and encryption configured on them, the session-by-session record of who used them, and the negative check that no instance is directly reachable instead via KSI-IAM-ELP
What NIST requires of SC-39
The control statement from NIST 800-53 Rev5, verbatim. Square brackets are organization-defined parameters — yours to set, not FedRAMP's to dictate.
Maintain a separate execution domain for each executing system process.
NIST SP 800-53 Rev5 catalog 5.2.0, from usnistgov/oscal-content at 78650f0. The FedRAMP dataset carries no control text; this is borrowed and pinned.
Rev5 baseline membership
Membership is the whole relationship — a baseline is a set of control ids. Class A carries no baseline at all. The Low/Moderate/High labels are an interpretation from control counts, not a dataset fact.
KSI indicators reaching this control (3)
Under 20x, these indicators are how this control is demonstrated — automated KSI evidence stands in for narrative control evidence.
- IAMKSI-IAM-ELPEnsuring Least Privilege
Identity and access management measures are used and persistently reviewed to ensure each user or device can only access the resources they need.
- IAMKSI-IAM-JITAuthorizing Just-in-Time
A least-privileged, role and attribute-based, and just-in-time security authorization model is used and persistently reviewed for all user and non-user accounts and services.
- SVCKSI-SVC-EISEvaluating and Improving Security
Information resources are persistently evaluated for opportunities to improve security and those improvements are persistently made.
Pages exist for the 209 controls reached by at least one KSI. Baseline-only controls are the orphans on /coverage. Control titles and full text live in the NIST catalog, not this dataset.